Skip to content

Conversation

@lbianc
Copy link

@lbianc lbianc commented Sep 1, 2017

The tc-print only uses two functions with arch code specific, which were
ported to PPC64 using the internal Decoder.
This implementation is still not good to send to facebook, since the target
of the branchs are not being dispayed and we need to think in a better
architectural solution, since it's using static "if" to switch the code.

The tc-print only uses two functions with arch code specific, which were
ported to PPC64 using the internal Decoder.
This implementation is still not good to send to facebook, since the target
of the branchs are not being dispayed and we need to think in a better
architectural solution, since it's using static "if" to switch the code.
@gromero
Copy link

gromero commented Sep 1, 2017

@lbianc Is there a way to check for the build log that indicates the conflict in question?

@lbianc
Copy link
Author

lbianc commented Sep 4, 2017

@gromero This does not came from the build, the github show the conflict automatically. Not sure if I answered your question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants