From: "Kjeld Borch Egevang" <kjelde@mips.com>
To: <linux-mips@oss.sgi.com>
Subject: RE: Error in gcc version 2.96 20000731
Date: Thu, 13 Sep 2001 22:47:25 +0200 [thread overview]
Message-ID: <NFBBKGGKGLLGNBGCEPKIAEHDCAAA.kjelde@mips.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1010913171138.4511A-100000@delta.ds2.pg.gda.pl>
Thanks for your reply.
I was trying to port SPEC CPU 2000 (benchmarks), and one of the tests
failed. I boiled it down to the attached program. For performance reasons it
could be perfectly valid not to use memset(), but I agree that the code
looks a bit odd.
/Kjeld
-----Original Message-----
From: Maciej W. Rozycki [mailto:macro@ds2.pg.gda.pl]
Sent: 13. september 2001 17:15
To: Kjeld Borch Egevang
Cc: linux-mips@oss.sgi.com
Subject: Re: Error in gcc version 2.96 20000731
On Thu, 13 Sep 2001, Kjeld Borch Egevang wrote:
> I discovered an optimization error in the current gcc for MIPS.
Is 2.96 20000731 current? I thought 3.0.1 is.
> When I compile the code below with -O2 it clears the code-field just
> after setting it. The instructions are mixed up. It works fine with -O1
> and -O0.
Use "-fno-strict-aliasing"?
> If the "//" is removed in front of the first printf, it works too.
Why don't you use memset() to clear the struct in the first place?
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
WARNING: multiple messages have this Message-ID (diff)
From: "Kjeld Borch Egevang" <kjelde@mips.com>
To: linux-mips@oss.sgi.com
Subject: RE: Error in gcc version 2.96 20000731
Date: Thu, 13 Sep 2001 22:47:25 +0200 [thread overview]
Message-ID: <NFBBKGGKGLLGNBGCEPKIAEHDCAAA.kjelde@mips.com> (raw)
Message-ID: <20010913204725.90eurt9vrAHTOPp6Yv345b3RHOix4AkOV5aNv1WqPMw@z> (raw)
In-Reply-To: <Pine.GSO.3.96.1010913171138.4511A-100000@delta.ds2.pg.gda.pl>
Thanks for your reply.
I was trying to port SPEC CPU 2000 (benchmarks), and one of the tests
failed. I boiled it down to the attached program. For performance reasons it
could be perfectly valid not to use memset(), but I agree that the code
looks a bit odd.
/Kjeld
-----Original Message-----
From: Maciej W. Rozycki [mailto:macro@ds2.pg.gda.pl]
Sent: 13. september 2001 17:15
To: Kjeld Borch Egevang
Cc: linux-mips@oss.sgi.com
Subject: Re: Error in gcc version 2.96 20000731
On Thu, 13 Sep 2001, Kjeld Borch Egevang wrote:
> I discovered an optimization error in the current gcc for MIPS.
Is 2.96 20000731 current? I thought 3.0.1 is.
> When I compile the code below with -O2 it clears the code-field just
> after setting it. The instructions are mixed up. It works fine with -O1
> and -O0.
Use "-fno-strict-aliasing"?
> If the "//" is removed in front of the first printf, it works too.
Why don't you use memset() to clear the struct in the first place?
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2001-09-13 20:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 14:15 Error in gcc version 2.96 20000731 Kjeld Borch Egevang
2001-09-13 15:10 ` H . J . Lu
2001-09-13 21:09 ` Kjeld Borch Egevang
2001-09-13 21:09 ` Kjeld Borch Egevang
2001-09-13 21:14 ` H . J . Lu
2001-09-13 21:22 ` Kjeld Borch Egevang
2001-09-13 21:22 ` Kjeld Borch Egevang
2001-09-13 21:26 ` H . J . Lu
2001-09-13 15:14 ` Maciej W. Rozycki
2001-09-13 15:16 ` H . J . Lu
2001-09-13 20:47 ` Kjeld Borch Egevang [this message]
2001-09-13 20:47 ` Kjeld Borch Egevang
2001-09-14 14:42 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NFBBKGGKGLLGNBGCEPKIAEHDCAAA.kjelde@mips.com \
--to=kjelde@mips.com \
--cc=linux-mips@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox