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/50299] New: entryval: bigendian 32bit->64bit extension breaks address match Date: Mon, 05 Sep 2011 18:13:00 -0000 [thread overview] Message-ID: <bug-50299-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50299 Bug #: 50299 Summary: entryval: bigendian 32bit->64bit extension breaks address match Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: jan.kratochvil@redhat.com CC: jakub@gcc.gnu.org Target: s390x-rhel62-linux-gnu archer-jankratochvil-entryval: f (r1=r1@entry=1, r2=r2@entry=2, r3=r3@entry=3, r4=r4@entry=4, r5=r5@entry=5, s1=11) at 1.c:5 5 } (gdb) p s1@entry Cannot find matching parameter at DW_TAG_GNU_call_site 0x80000516 at main static void __attribute__ ((noinline, noclone)) f (int r1, int r2, int r3, int r4, int r5, int s1) { asm volatile ("" ::: "memory"); } int main (void) { f (1, 2, 3, 4, 5, 11); return 0; } -Wall -g -O2 gcc (GCC) 4.7.0 20110805 (experimental) In main() it is 8 bytes at %r15+160 but in f() it is 4 bytes at %r15+164. 160 != 164 and GDB cannot know how many bytes it is in main(), there is no parameter width anywhere there. 80000502: e3 10 f0 a0 00 24 stg %r1,160(%r15) 80000510: c0 e5 ff ff ff ea brasl %r14,800004e4 <f> <2><c3>: Abbrev Number: 6 (DW_TAG_GNU_call_site) <c4> DW_AT_low_pc : 0x80000516 <cc> DW_AT_abstract_origin: <0x31> <3><ea>: Abbrev Number: 7 (DW_TAG_GNU_call_site_parameter) <eb> DW_AT_location : 3 byte block: 7f a0 1 (DW_OP_breg15 (r15): 160) <ef> DW_AT_GNU_call_site_value: 1 byte block: 3b (DW_OP_lit11) <2><8c>: Abbrev Number: 3 (DW_TAG_formal_parameter) <8d> DW_AT_name : s1 <92> DW_AT_type : <0x9a> <96> DW_AT_location : 2 byte block: 91 4 (DW_OP_fbreg: 4) <1><9a>: Abbrev Number: 4 (DW_TAG_base_type) <9b> DW_AT_byte_size : 4 <9d> DW_AT_name : int <1><31>: Abbrev Number: 2 (DW_TAG_subprogram) <32> DW_AT_name : f <47> DW_AT_frame_base : 3 byte block: 7f a0 1 (DW_OP_breg15 (r15): 160)
next reply other threads:[~2011-09-05 18:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-05 18:13 jan.kratochvil at redhat dot com [this message] 2011-09-05 18:33 ` [Bug debug/50299] " jakub at gcc dot gnu.org 2011-09-06 11:22 ` jakub at gcc dot gnu.org 2011-09-07 11:07 ` jan.kratochvil at redhat dot com 2011-09-12 16:18 ` jakub at gcc dot gnu.org 2011-09-12 16:39 ` jakub 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-50299-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).