public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/53948] New: [4.8 Regression] Assignment line missing for -O0 -g Date: Fri, 13 Jul 2012 08:51:00 -0000 [thread overview] Message-ID: <bug-53948-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53948 Bug #: 53948 Summary: [4.8 Regression] Assignment line missing for -O0 -g Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: jan.kratochvil@redhat.com CC: aoliva@gcc.gnu.org Target: x86_64-unknown-linux-gnu Nothing serious but it broke gdb.base/store.exp and I believe -O0 -g should not "optimize out" source statements. int f (register int a, register int b) { register int x = b, y = a; return x + y; } gcc -g PASS: gcc (GCC) 4.7.2 20120713 (prerelease) 7: 89 f8 mov %edi,%eax 9: 89 f2 mov %esi,%edx register int x = b, y = a; b: 41 89 d4 mov %edx,%r12d e: 89 c3 mov %eax,%ebx return x + y; } 10: 41 8d 04 1c lea (%r12,%rbx,1),%eax FAIL: gcc (GCC) 4.8.0 20120713 (experimental) 7: 89 fb mov %edi,%ebx 9: 41 89 f4 mov %esi,%r12d register int x = b, y = a; return x + y; } c: 41 8d 04 1c lea (%r12,%rbx,1),%eax GDB no longer stops on the 'register int x = b, y = a;' line during 'step'. .debug_info is correct in both cases. I can update the GDB testsuite but still I believe 'int var = val;' source line should have its instruction during -O0 -g, even if it is just a 'nop'.
next reply other threads:[~2012-07-13 8:51 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-13 8:51 jan.kratochvil at redhat dot com [this message] 2012-07-13 9:12 ` [Bug debug/53948] " rguenth at gcc dot gnu.org 2012-07-16 19:37 ` jakub at gcc dot gnu.org 2012-07-16 19:49 ` steven at gcc dot gnu.org 2012-07-16 20:23 ` steven at gcc dot gnu.org 2012-07-16 21:58 ` steven at gcc dot gnu.org 2012-09-19 13:45 ` rguenth at gcc dot gnu.org 2013-02-07 20:05 ` law at redhat dot com 2013-02-07 20:24 ` stevenb.gcc at gmail dot com 2013-02-07 20:41 ` jakub at gcc dot gnu.org 2013-02-07 20:47 ` law at redhat dot com 2013-02-08 8:28 ` rguenth at gcc dot gnu.org 2013-02-08 13:20 ` law at redhat dot com 2013-02-08 13:46 ` jakub at gcc dot gnu.org 2013-02-08 20:04 ` law at gcc dot gnu.org 2013-02-08 20:05 ` law at redhat dot com 2013-02-08 20:07 ` law at redhat dot com
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-53948-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: linkBe 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).