toolchain's output depends on toolchain used to build the compiler?

toolchain's output depends on toolchain used to build the compiler?

Yedidyah Bar-David linux-il at didi.bardavid.org
Wed Feb 10 08:37:47 IST 2010


On Wed, Feb 10, 2010 at 04:06:32AM +0200, Shachar Shemesh wrote:
> Again, thank you for trying to help, but lets try to move forward.

Well, you obviously expected an answer from someone that either knows
gcc well enough to give an answer off the top of their head, or from
someone that such a thing already happened to them and managed to find
the reason/a solution. I think you can say that there are none of
these on this list. So either:
1. Look elsewhere (in some gcc-specific list, for example)
2. Give up and start debugging gcc yourself
3. Give us some more clues. This practically means a short example
where this happens. Since you have the sources that compile differently,
you might try to find out e.g. if taking just the function(s) that
compiled differently and putting them in their own file still compiles
them differently, and then post them (or something similar) (with your
client's permission, if applicable). I know that gcc can optimize on
a larger scope than a function, but this might work.
-- 
Didi




More information about the Linux-il mailing list