From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Diego Novillo <dnovillo@redhat.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Daily snapshots of tree-ssa branch available
Date: Tue, 13 May 2003 20:32:00 -0000 [thread overview]
Message-ID: <3EC1559C.8080601@moene.indiv.nluug.nl> (raw)
In-Reply-To: <3EC01D91.8060703@moene.indiv.nluug.nl>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
Toon Moene wrote:
> Diego Novillo wrote:
>
>> On Sat, 2003-05-10 at 04:06, Toon Moene wrote:
>>> Oh, and you need about a dozen no-warn entries added to
>>> gcc/gcc/Makefile.in :-(
>>
>> Yes. This is an issue we need to fix before merging into mainline.
>> GIMPLE tends to emit conditionals that trigger warnings like 'used
>> before definition'. I believe that Jason was working on a change that
>> would fix this. In any case, for now they are OK to list as no-warn,
>> but we will need to remove those settings before merging. Could you add
>> these entries near the existing FIXME note when you patch Makefile.in?
>
> Will work on that when I find some time ...
Here ya go:
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://gcc-g95.sourceforge.net/ (under construction)
[-- Attachment #2: make.patch --]
[-- Type: text/plain, Size: 1513 bytes --]
2003-05-13 Toon Moene <toon@moene.indiv.nluug.nl>
* Makefile.in: Add additional -Wno-error targets for Alpha.
*** Makefile.in.orig Tue May 13 17:54:16 2003
--- Makefile.in Tue May 13 19:29:14 2003
*************** gengtype-lex.o-warn = -Wno-error
*** 172,177 ****
--- 172,182 ----
# the gimplifier re-writes va_start with a temporary instead of using the
# last named argument of the function.
+ alias.o-warn = -Wno-error
bitmap.o-warn = -Wno-error
+ builtins.o-warn = -Wno-error
+ caller-save.o-warn = -Wno-error
combine.o-warn = -Wno-error
+ cfgrtl.o-warn = -Wno-error
+ cse.o-warn = -Wno-error
c-semantics.o-warn = -Wno-error
c-typeck.o-warn = -Wno-error
*************** emit-rtl.o-warn = -Wno-error
*** 180,184 ****
--- 185,196 ----
expr.o-warn = -Wno-error
fold-const.o-warn = -Wno-error
+ ifcvt.o-warn = -Wno-error
genattrtab.o-warn = -Wno-error
+ jump.o-warn = -Wno-error
+ local-alloc.o-warn = -Wno-error
+ ra-build.o-warn = -Wno-error
+ simplify-rtx.o-warn = -Wno-error
+ sched-vis.o-warn = -Wno-error
+ stmt.o-warn = -Wno-error
reload1.o-warn = -Wno-error
reload.o-warn = -Wno-error
*************** rtlanal.o-warn = -Wno-error
*** 186,190 ****
--- 198,206 ----
tree.o-warn = -Wno-error
varasm.o-warn = -Wno-error
+ f/com.o-warn = -Wno-error
+ f/equiv.o-warn = -Wno-error
f/expr.o-warn = -Wno-error
+ f/intrin.o-warn = -Wno-error
+ f/where.o-warn = -Wno-error
# The warning for 'prev_file_name' in profile.c is odd. The variable *is*
# initialized before being used.
next prev parent reply other threads:[~2003-05-13 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 15:18 Diego Novillo
2003-05-10 8:04 ` Toon Moene
2003-05-12 12:43 ` Diego Novillo
2003-05-12 17:04 ` Joe Buck
2003-05-13 14:52 ` Diego Novillo
2003-05-12 22:17 ` Toon Moene
2003-05-12 23:14 ` Diego Novillo
2003-05-13 20:32 ` Toon Moene [this message]
2003-05-14 12:46 ` Diego Novillo
2003-05-21 16:25 ` Jason Merrill
2003-05-22 6:03 ` Toon Moene
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=3EC1559C.8080601@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=dnovillo@redhat.com \
--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).