From: "Paulo J. Matos" <paulo@matos-sorge.com>
To: gcc@gcc.gnu.org
Subject: Re: Volatile qualification on pointer and data
Date: Fri, 23 Sep 2011 11:51:00 -0000 [thread overview]
Message-ID: <j5hrre$95o$1@dough.gmane.org> (raw)
In-Reply-To: <j5hqpt$1uu$1@dough.gmane.org>
On 23/09/11 12:33, Paulo J. Matos wrote:
> On 22/09/11 22:15, Richard Guenther wrote:
>>
>> Btw, I think this is an old bug that has been resolved. Did you make
>> sure to
>> test a recent 4.6 branch snapshot or svn head?
>>
>
> Should have tested git head. Compiling git head now to check the current
> status of this issue.
>
>
Git head 36181f98f doesn't compile (x86_64, --enable-checking=all, GCC
4.5.2):
gcc -c -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -Wold-style-definition -Wc++-compat -fno-common
-DHAVE_CONFIG_H -I. -I. -I../../../repositories/gcc/gcc
-I../../../repositories/gcc/gcc/.
-I../../../repositories/gcc/gcc/../include
-I../../../repositories/gcc/gcc/../libcpp/include
-I../../../repositories/gcc/gcc/../libdecnumber
-I../../../repositories/gcc/gcc/../libdecnumber/bid -I../libdecnumber
../../../repositories/gcc/gcc/fold-const.c -o fold-const.o
../../../repositories/gcc/gcc/fold-const.c: In function
‘fold_overflow_warning’:
../../../repositories/gcc/gcc/fold-const.c:326:5: warning: format not a
string literal and no format arguments
../../../repositories/gcc/gcc/fold-const.c: In function
‘fold_checksum_tree’:
../../../repositories/gcc/gcc/fold-const.c:13803:3: error: invalid
application of ‘sizeof’ to incomplete type ‘struct tree_type’
--
PMatos
next prev parent reply other threads:[~2011-09-23 11:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 16:08 Paulo J. Matos
2011-09-20 16:36 ` Ian Lance Taylor
2011-09-21 7:07 ` David Brown
2011-09-21 8:22 ` Paulo J. Matos
2011-09-21 10:20 ` David Brown
2011-09-21 13:57 ` Ian Lance Taylor
2011-09-21 14:25 ` David Brown
2011-09-21 14:57 ` Paulo J. Matos
2011-09-22 8:39 ` David Brown
2011-09-22 21:15 ` Richard Guenther
2011-09-23 11:33 ` Paulo J. Matos
2011-09-23 11:51 ` Paulo J. Matos [this message]
2011-09-23 13:17 ` Paulo J. Matos
2011-09-21 18:51 ` Georg-Johann Lay
2011-09-22 8:53 ` David Brown
2011-09-24 15:10 ` John Regehr
2011-09-24 15:49 ` David Brown
2011-09-24 16:26 ` David Brown
2011-09-24 19:38 ` John Regehr
2011-09-25 13:03 ` David Brown
2011-09-25 15:15 ` Andreas Schwab
2011-09-25 16:33 ` David Brown
2011-09-25 16:36 ` David Brown
2011-09-25 16:06 ` Dave Korn
2011-09-25 22:05 ` David Brown
2011-09-25 22:05 ` David Brown
2011-09-26 7:14 ` Miles Bader
2011-09-26 8:53 ` David Brown
2011-09-26 8:58 ` David Brown
2011-09-21 8:14 ` Paulo J. Matos
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='j5hrre$95o$1@dough.gmane.org' \
--to=paulo@matos-sorge.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).