public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/32395] false positive warning about use of uninitialized variable.
Date: Thu, 27 Sep 2007 00:58:00 -0000	[thread overview]
Message-ID: <20070927005802.17288.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32395-7667@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]



------- Comment #11 from manu at gcc dot gnu dot org  2007-09-27 00:58 -------
(In reply to comment #10)
> Manuel, ping, do you working on it?
> i've posted preprocessed 32-bit testaces for you over month ago ;)
> btw. PR32368 exposes this bug.
> 

Sorry, I am probably doing something wrong but I cannot get it to compile.
Weird.

manuel@gcc11:~$ 128590/build/gcc/cc1plus src/multi_index_test.ii -O1 -Wall
-Wfatal-errors
In file included from /usr/include/c++/4.2.1/bits/stl_algobase.h:73,
                 from /usr/include/c++/4.2.1/algorithm:66,
                 from /usr/include/boost/multi_index_container.hpp:20,
                 from multi_index_test.cpp:2:
/usr/include/c++/4.2.1/bits/cpp_type_traits.h: At global scope:
/usr/include/c++/4.2.1/bits/cpp_type_traits.h:346: error: expected identifier
before ‘__is_pod’

and

manu@localhost:~/$ g++ -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)

manu@localhost:~/$ g++ -Wall -O1 -c multi_index_test.ii -Wfatal-errors
/usr/include/c++/4.2.1/x86_64-pld-linux/32/bits/c++config.h:149: error:
expected `=' before ‘__attribute__’
compilation terminated due to -Wfatal-errors.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32395


  parent reply	other threads:[~2007-09-27  0:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 17:24 [Bug c++/32395] New: " pluto at agmk dot net
2007-06-18 17:25 ` [Bug c++/32395] " pluto at agmk dot net
2007-06-19  8:10 ` [Bug middle-end/32395] " pinskia at gcc dot gnu dot org
2007-06-24 15:54 ` pluto at agmk dot net
2007-06-25 22:56 ` pluto at agmk dot net
2007-06-25 22:57 ` pluto at agmk dot net
2007-08-22 15:44 ` manu at gcc dot gnu dot org
2007-08-22 15:54 ` pluto at agmk dot net
2007-08-22 16:48 ` manu at gcc dot gnu dot org
2007-08-22 18:36 ` pluto at agmk dot net
2007-09-25 14:24 ` pluto at agmk dot net
2007-09-27  0:58 ` manu at gcc dot gnu dot org [this message]
2007-09-27  4:07 ` bangerth at dealii dot org
2008-01-08 20:00 ` pluto at agmk dot net
2008-01-23 21:25 ` pluto at agmk dot net
2008-01-23 23:20 ` manu at gcc dot gnu dot org
2008-02-01 17:56 ` manu at gcc dot gnu dot org
2010-03-15 10:32 ` [Bug middle-end/32395] false uninitialized warning (huge testcase) pluto at agmk dot net
2010-03-15 13:40 ` manu at gcc dot gnu dot org

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=20070927005802.17288.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).