From: "Nuesser, Wilhelm" <wilhelm.nuesser@sap.com>
To: "'Jim Wilson'" <wilson@cygnus.com>
Cc: gcc@gcc.gnu.org
Subject: RE: Bug report optimization #4186 and ia64
Date: Tue, 25 Sep 2001 01:40:00 -0000 [thread overview]
Message-ID: <816D93CCC927D31188570008C75D1DE106DEA5F2@dbwdfx1a.wdf.sap-ag.de> (raw)
Hi,
> -----Original Message-----
> From: Jim Wilson [ mailto:wilson@cygnus.com ]
> I took a look at PR 4186. It is an x86 sibling-call optimization bug.
> We accidentally overwrite one of the incoming function
> arguments before
> reading it in the sibling call sequence. I put this info into the PR.
Thanks a lot for your quick response. We will re-build or entire
app asap and check this.
> I think it is unlikely that the IA-64 problem is related, since the
> IA-64 does not pass arguments on the stack like the x86 does.
You're right. We checked this with -fno-optimize-sibling-calls and
- independently - with -fno-strict-aliasing as H.J. Lu suggested.
Neither of them showed any effect.
We'll have to look futher into a testcase.
Thanks
Willi
next reply other threads:[~2001-09-25 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 1:40 Nuesser, Wilhelm [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 7:03 Willi NüÃer
2001-09-24 12:50 ` Jim Wilson
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=816D93CCC927D31188570008C75D1DE106DEA5F2@dbwdfx1a.wdf.sap-ag.de \
--to=wilhelm.nuesser@sap.com \
--cc=gcc@gcc.gnu.org \
--cc=wilson@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).