From: Giuliano Pochini <pochini@shiny.it>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: RE: another difference in gcc (2v) ?
Date: Wed, 11 Apr 2001 17:55:19 +0200 (CEST) [thread overview]
Message-ID: <XFMail.010411175519.pochini@shiny.it> (raw)
In-Reply-To: <200104111415.f3BEFkQ28728@ashley.ivey.uwo.ca>
> Lost in the huge diff was one other change, this time in the actual code
> itself.
>
> Can anyone tell me if this code resequence is legal? The diff (-) lines
> show the nonworking disassembled code (generated by -O2) while the
> diff's (+) lines show the working code (generated by -O2
> -fno-schedule-insns -fno-schedule-insns2. [...]
> Is this a correct resequence ?
The two sequences seems equivalent IMHO.
Bye.
Giuliano Pochini ->)|(<- Shiny Network {AS6665} ->)|(<-
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-11 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 14:15 another difference in gcc (2v) ? Kevin B. Hendricks
2001-04-11 14:56 ` David Edelsohn
2001-04-11 16:23 ` Florin Boariu
2001-04-11 15:21 ` Jerry Van Baren
2001-04-11 15:22 ` Gabriel Paubert
2001-04-11 15:55 ` Giuliano Pochini [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-12 2:46 nolan
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=XFMail.010411175519.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 NNTP newsgroup(s).