From: dewar@gnat.com
To: charlet@ACT-Europe.FR, guerby@acm.org
Cc: gcc@gcc.gnu.org, jbuck@synopsys.COM, pkoning@equallogic.com,
torvalds@transmeta.com
Subject: Re: Optimizations on long long multiply/divide on PowerPC32 don't
Date: Tue, 11 Dec 2001 06:23:00 -0000 [thread overview]
Message-ID: <20011211141208.A446FF28CD@nile.gnat.com> (raw)
<<If I understand correctly, Inline_Always not inlining at -O0 is
considered a bug. Any available test case or description for the
subtle issues you mention?
>>
Yes, we consider that a bug
next reply other threads:[~2001-12-11 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 6:23 dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-10 10:23 Optimizations on long long multiply/divide on PowerPC32 don't work Linus Torvalds
2001-12-10 11:35 ` Optimizations on long long multiply/divide on PowerPC32 don't Joe Buck
2001-12-10 13:49 ` guerby
2001-12-10 14:08 ` Arnaud Charlet
2001-12-10 14:31 ` guerby
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=20011211141208.A446FF28CD@nile.gnat.com \
--to=dewar@gnat.com \
--cc=charlet@ACT-Europe.FR \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.org \
--cc=jbuck@synopsys.COM \
--cc=pkoning@equallogic.com \
--cc=torvalds@transmeta.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).