On Fri, Mar 28, 2008 at 5:52 PM, Denys Vlasenko
<[EMAIL PROTECTED]> wrote:
> In this case I used it as an example why expecting gcc
> (and probably any other compiler) to generate
> ideantical assembly from same source on different OS
> is unrealistic.
You can generate identical assembly from
On Saturday 29 March 2008 01:46, Andrew Pinski wrote:
> On Fri, Mar 28, 2008 at 5:16 PM, Denys Vlasenko
> <[EMAIL PROTECTED]> wrote:
> > See:
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29950
>
> And I can tell you now that bug is on purpose and really not a bug.
> We base stuff on the d
On Fri, Mar 28, 2008 at 5:16 PM, Denys Vlasenko
<[EMAIL PROTECTED]> wrote:
> See:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29950
And I can tell you now that bug is on purpose and really not a bug.
We base stuff on the decl uid and not memory address so we try for the
same code on differen
On Fri, Mar 28, 2008 at 04:56:52PM -0700, Alexandra (Sasha) Fedorova wrote:
> I was wondering anyone knows any details of the gcc port for Solaris/x86.
> I am wondering, if I have an executable compiled with gcc for Linux and an
> executable compiled with the same gcc (same version, same options)
On Saturday 29 March 2008 00:56, Alexandra (Sasha) Fedorova wrote:
> I was wondering anyone knows any details of the gcc port for Solaris/x86.
> I am wondering, if I have an executable compiled with gcc for Linux and an
> executable compiled with the same gcc (same version, same options) for
> S
I was wondering anyone knows any details of the gcc port for Solaris/x86.
I am wondering, if I have an executable compiled with gcc for Linux and an
executable compiled with the same gcc (same version, same options) for
Solaris, how similar would those executables be? I understand that the
code
