public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/58767] New: assemly output (labels order) depends on the sources location.
Date: Thu, 17 Oct 2013 09:48:00 -0000 [thread overview]
Message-ID: <bug-58767-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58767
Bug ID: 58767
Summary: assemly output (labels order) depends on the sources
location.
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: pluto at agmk dot net
Created attachment 31025
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31025&action=edit
testcase
hi,
on the attached testcase you can see that location
of LASF{10,12,28} in the output assembly varies.
this prevents ccache from reuse objects.
LASF24 content change is not a problem and can be unified
in the other way.
$ ./bug.sh
+ rm -f t1.s t2.s
+ CXXFLAGS='-Wall -gno-record-gcc-switches -g2 -gdwarf-4 --save-temps'
+ g++ -Wall -gno-record-gcc-switches -g2 -gdwarf-4 --save-temps
repo/branch1/t.cpp -S
+ mv t.s t1.s
+ mv t.ii t1.ii
+ g++ -Wall -gno-record-gcc-switches -g2 -gdwarf-4 --save-temps
repo/branch2/t.cpp -S
+ mv t.s t2.s
+ mv t.ii t2.ii
+ diff -u t1.s t2.s
--- t1.s 2013-10-17 11:38:03.084369344 +0200
+++ t2.s 2013-10-17 11:38:03.177702172 +0200
@@ -407,6 +407,8 @@
.string "nothrow_t"
.LASF22:
.string "bool"
+.LASF12:
+ .string "signed char"
.LASF18:
.string "float"
.LASF5:
@@ -423,16 +425,14 @@
.string "__gnu_debug"
.LASF2:
.string "__gnu_cxx"
-.LASF12:
- .string "signed char"
+.LASF24:
+ .string "repo/branch2/t.cpp"
.LASF11:
.string "long long unsigned int"
.LASF9:
.string "unsigned int"
.LASF32:
.string "_ZN9__gnu_cxx24__numeric_traits_integerIlE5__maxE"
-.LASF10:
- .string "long unsigned int"
.LASF8:
.string "short unsigned int"
.LASF21:
@@ -445,8 +445,8 @@
.string "GNU C++ 4.8.1 20130531 (release)"
.LASF4:
.string "__max"
-.LASF28:
- .string "nothrow"
+.LASF10:
+ .string "long unsigned int"
.LASF17:
.string "double"
.LASF3:
@@ -457,7 +457,7 @@
.string "__debug"
.LASF6:
.string "__digits"
-.LASF24:
- .string "repo/branch1/t.cpp"
+.LASF28:
+ .string "nothrow"
.ident "GCC: (PLD-Linux) 4.8.1 20130531 (release)"
.section .note.GNU-stack,"",@progbits
next reply other threads:[~2013-10-17 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 9:48 pluto at agmk dot net [this message]
2021-12-06 4:57 ` [Bug debug/58767] " pinskia 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-58767-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).