public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/56154] [4.7/4.8 Regression] Bad .debug_loc generated for some code
Date: Wed, 30 Jan 2013 17:17:00 -0000 [thread overview]
Message-ID: <bug-56154-4-kJ6QN35X6b@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56154-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56154
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-30 17:16:08 UTC ---
Created attachment 29308
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29308
gcc48-pr56154.patch
Untested fix, together with guality testcases that show the issue. On x86_64,
without the dwarf2out.c change I see with:
make check-gcc \
RUNTESTFLAGS='--target_board=unix\{-m32,-m64\} guality.exp=pr56154*.c'
Running target unix/-m32
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /usr/src/gcc/gcc/testsuite/config/default.exp as tool-and-target-specific
interface file.
Running /usr/src/gcc/gcc/testsuite/gcc.dg/guality/guality.exp ...
FAIL: gcc.dg/guality/pr56154-2.c -O1 line pr56154-2.c:30 x == 28
FAIL: gcc.dg/guality/pr56154-2.c -O2 line pr56154-2.c:30 x == 28
FAIL: gcc.dg/guality/pr56154-2.c -O3 -fomit-frame-pointer line pr56154-2.c:30
x == 28
FAIL: gcc.dg/guality/pr56154-2.c -O3 -g line pr56154-2.c:30 x == 28
FAIL: gcc.dg/guality/pr56154-3.c -O1 line pr56154-3.c:22 x == 28
FAIL: gcc.dg/guality/pr56154-3.c -O2 line pr56154-3.c:22 x == 28
FAIL: gcc.dg/guality/pr56154-3.c -O3 -fomit-frame-pointer line pr56154-3.c:22
x == 28
FAIL: gcc.dg/guality/pr56154-3.c -O3 -g line pr56154-3.c:22 x == 28
Running target unix/-m64
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /usr/src/gcc/gcc/testsuite/config/default.exp as tool-and-target-specific
interface file.
Running /usr/src/gcc/gcc/testsuite/gcc.dg/guality/guality.exp ...
FAIL: gcc.dg/guality/pr56154-1.c -O1 line pr56154-1.c:17 x.a == 4
FAIL: gcc.dg/guality/pr56154-1.c -O1 line pr56154-1.c:20 x.a == 6
FAIL: gcc.dg/guality/pr56154-1.c -O2 line pr56154-1.c:17 x.a == 4
FAIL: gcc.dg/guality/pr56154-1.c -O2 line pr56154-1.c:20 x.a == 6
FAIL: gcc.dg/guality/pr56154-1.c -O3 -fomit-frame-pointer line pr56154-1.c:17
x.a == 4
FAIL: gcc.dg/guality/pr56154-1.c -O3 -fomit-frame-pointer line pr56154-1.c:20
x.a == 6
FAIL: gcc.dg/guality/pr56154-1.c -O3 -g line pr56154-1.c:17 x.a == 4
FAIL: gcc.dg/guality/pr56154-1.c -O3 -g line pr56154-1.c:20 x.a == 6
FAIL: gcc.dg/guality/pr56154-1.c -Os line pr56154-1.c:17 x.a == 4
FAIL: gcc.dg/guality/pr56154-1.c -Os line pr56154-1.c:20 x.a == 6
FAIL: gcc.dg/guality/pr56154-2.c -O1 line pr56154-2.c:30 x == 28
FAIL: gcc.dg/guality/pr56154-2.c -O2 line pr56154-2.c:30 x == 28
FAIL: gcc.dg/guality/pr56154-2.c -O3 -fomit-frame-pointer line pr56154-2.c:30
x == 28
FAIL: gcc.dg/guality/pr56154-2.c -O3 -g line pr56154-2.c:30 x == 28
FAIL: gcc.dg/guality/pr56154-2.c -Os line pr56154-2.c:30 x == 28
FAIL: gcc.dg/guality/pr56154-3.c -O1 line pr56154-3.c:22 x == 28
FAIL: gcc.dg/guality/pr56154-3.c -O2 line pr56154-3.c:22 x == 28
FAIL: gcc.dg/guality/pr56154-3.c -O3 -fomit-frame-pointer line pr56154-3.c:22
x == 28
FAIL: gcc.dg/guality/pr56154-3.c -O3 -g line pr56154-3.c:22 x == 28
FAIL: gcc.dg/guality/pr56154-3.c -Os line pr56154-3.c:22 x == 28
while with it everything passes.
next prev parent reply other threads:[~2013-01-30 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 15:53 [Bug debug/56154] New: " jakub at gcc dot gnu.org
2013-01-30 17:17 ` jakub at gcc dot gnu.org [this message]
2013-01-30 17:22 ` [Bug debug/56154] " jakub at gcc dot gnu.org
2013-02-07 14:49 ` jakub at gcc dot gnu.org
2013-02-07 15:19 ` [Bug debug/56154] [4.7 " jakub at gcc dot gnu.org
2013-04-03 9:50 ` rguenth at gcc dot gnu.org
2013-04-11 7:59 ` rguenth at gcc dot gnu.org
2014-06-12 13: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-56154-4-kJ6QN35X6b@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).