public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "galtgendo at o2 dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53707] New: compiler generates wrong code
Date: Sun, 17 Jun 2012 13:00:00 -0000 [thread overview]
Message-ID: <bug-53707-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53707
Bug #: 53707
Summary: compiler generates wrong code
Classification: Unclassified
Product: gcc
Version: 4.6.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: galtgendo@o2.pl
Using built-in specs.
COLLECT_GCC=gcc-4.6.3
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/4.6.3/lto-wrapper
Target: i686-pc-linux-gnu
Configured with:
/mnt/workbox/builds/portage/sys-devel/gcc-4.6.3/work/gcc-4.6.3/configure
--prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.6.3
--includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.6.3/include
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.3
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.3/man
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.3/info
--with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.6.3/include/g++-v4
--host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec
--disable-fixed-point --with-ppl --with-cloog --disable-ppl-version-check
--with-cloog-include=/usr/include/cloog-ppl --enable-lto --enable-nls
--without-included-gettext --with-system-zlib --disable-werror
--enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp
--enable-libgomp
--with-python-dir=/share/gcc-data/i686-pc-linux-gnu/4.6.3/python
--enable-checking=release --disable-libgcj --with-arch=i686 --enable-objc-gc
--enable-languages=c,c++,objc,fortran --enable-shared --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all
--with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.6.3 p1.3,
pie-0.5.1' --disable-libstdcxx-pch
Thread model: posix
gcc version 4.6.3 (Gentoo 4.6.3 p1.3, pie-0.5.1)
g++-4.6.3 -std=gnu++0x -O3 -fomit-frame-pointer -march=native -c tools.cpp -o
ui-tools.o
(without preprocessor switches, as they won't matter for preprocessed sources)
no warnings with the above line (though quite a few with -Wall, but not in the
affected part of code, it would seem)
The attached preprocessed sources produce *right* code, to get the *wrong*
code, remove 'string test(n);' (which should be a no-op there) from the
'for(unsigned n = 0; n < Codes; n++)' around line 54977.
next reply other threads:[~2012-06-17 13:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 13:00 galtgendo at o2 dot pl [this message]
2012-06-17 13:03 ` [Bug c++/53707] " galtgendo at o2 dot pl
2012-06-17 13:05 ` galtgendo at o2 dot pl
2012-06-17 13:09 ` galtgendo at o2 dot pl
2012-06-18 8:55 ` rguenth at gcc dot gnu.org
2012-06-18 9:46 ` galtgendo at o2 dot pl
2012-06-18 9:58 ` rguenth at gcc dot gnu.org
2012-06-18 9:59 ` rguenth at gcc dot gnu.org
2012-06-18 10:04 ` rguenth at gcc dot gnu.org
2012-06-18 10:44 ` galtgendo at o2 dot pl
2012-06-18 11:13 ` galtgendo at o2 dot pl
2012-07-02 19:38 ` galtgendo at o2 dot pl
2012-07-02 20:00 ` mikpe at it dot uu.se
2012-07-02 20:25 ` galtgendo at o2 dot pl
2012-07-03 5:02 ` jakub at gcc dot gnu.org
2012-07-03 9:56 ` mikpe at it dot uu.se
2012-07-03 13:09 ` pinskia at gcc dot gnu.org
2012-07-03 14:05 ` schwab@linux-m68k.org
2012-07-03 15:05 ` mikpe at it dot uu.se
2012-07-04 9:22 ` rguenth at gcc dot gnu.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=bug-53707-4@http.gcc.gnu.org/bugzilla/ \
--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).