From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: dnovillo@redhat.com (Diego Novillo)
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: tree-ssa branch: Call for preliminary testing
Date: Thu, 15 May 2003 17:50:00 -0000 [thread overview]
Message-ID: <200305151750.h4FHojXE000152@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <1052741333.27232.57.camel@frodo.toronto.redhat.com> from "Diego Novillo" at May 12, 2003 08:43:55 am
> This is due to GIMPLE. The gimplifier restructures the trees in ways
> that trigger false warnings like this one. This needs to be fixed but
> for now you can just add a no-warning entry for regmove.c in
> Makefile.in. There's a few of these already, they're clustered around a
> FIXME note that describes this problem.
I installed the enclosed patched. Tested on hppa-unknown-linux-gnu:
<http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00889.html>.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
2003-05-15 John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
* Makefile.in (regmove.o-warn): Change to -Wno-error.
Index: Makefile.in
===================================================================
RCS file: /cvs/gcc/gcc/gcc/Makefile.in,v
retrieving revision 1.903.2.91
diff -u -3 -p -r1.903.2.91 Makefile.in
--- Makefile.in 14 May 2003 19:43:38 -0000 1.903.2.91
+++ Makefile.in 14 May 2003 23:11:30 -0000
@@ -192,6 +192,7 @@ ra-build.o-warn = -Wno-error
simplify-rtx.o-warn = -Wno-error
sched-vis.o-warn = -Wno-error
stmt.o-warn = -Wno-error
+regmove.o-warn = -Wno-error
reload1.o-warn = -Wno-error
reload.o-warn = -Wno-error
rtlanal.o-warn = -Wno-error
next prev parent reply other threads:[~2003-05-15 17:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 2:13 John David Anglin
2003-05-12 12:43 ` Diego Novillo
2003-05-15 17:50 ` John David Anglin [this message]
2003-05-15 19:32 ` Diego Novillo
-- strict thread matches above, loose matches on Subject: below --
2003-05-11 17:11 Richard Guenther
2003-05-12 12:43 ` Diego Novillo
2003-05-12 12:58 ` Steven Bosscher
2003-05-12 13:08 ` Andrew MacLeod
2003-05-12 13:16 ` Diego Novillo
2003-05-12 13:22 ` Andrew MacLeod
2003-05-12 13:49 ` Richard Guenther
2003-05-12 14:05 ` Daniel Berlin
2003-05-12 14:16 ` Andrew MacLeod
2003-05-12 14:17 ` Diego Novillo
2003-06-12 15:36 ` Diego Novillo
2003-05-12 13:02 ` Richard Guenther
2003-06-12 16:09 ` Diego Novillo
2003-06-12 21:10 ` Richard Guenther
2003-06-12 21:29 ` Diego Novillo
2003-06-13 9:58 ` Richard Guenther
2003-06-13 11:38 ` Diego Novillo
2003-06-14 11:41 ` Richard Guenther
2003-06-13 20:15 ` Andrew MacLeod
2003-06-14 20:06 ` Richard Guenther
2003-05-12 13:02 ` Steven Bosscher
2003-05-12 13:09 ` Diego Novillo
2003-05-12 13:59 ` Daniel Berlin
2003-05-12 14:12 ` Andrew MacLeod
2003-05-07 14:25 Diego Novillo
2003-05-07 14:30 ` Diego Novillo
2003-05-07 17:54 ` Qiong Cai
2003-05-07 18:02 ` law
2003-05-09 1:31 ` Qiong Cai
2003-05-09 2:02 ` Andrew Pinski
2003-05-07 18:24 ` Daniel Berlin
2003-05-08 5:51 ` Toon Moene
2003-05-08 13:26 ` Diego Novillo
2003-05-09 16:46 ` Gerald Pfeifer
2003-05-09 17:28 ` Diego Novillo
2003-05-09 17:37 ` Diego Novillo
2003-05-09 19:02 ` Eric Botcazou
2003-05-10 14:19 ` Gerald Pfeifer
2003-05-10 14:43 ` Graham Stott
2003-05-10 15:34 ` Daniel Berlin
2003-05-12 12:43 ` Diego Novillo
2003-05-10 15:04 ` Gerald Pfeifer
2003-05-12 14:21 ` Gerald Pfeifer
2003-05-12 16:27 ` Steven Bosscher
2003-05-20 10:44 ` Gerald Pfeifer
2003-05-20 11:39 ` Diego Novillo
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=200305151750.h4FHojXE000152@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=dnovillo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).