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/48163] [4.7 Regression]: ICEs for cris-elf, like gcc.c-torture/compile/calls.c gcc.c-torture/execute/complex-1.c Date: Thu, 17 Mar 2011 12:07:00 -0000 [thread overview] Message-ID: <bug-48163-4-cUqbLFL6sZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48163-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48163 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2011.03.17 12:04:00 AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-17 12:04:00 UTC --- Created attachment 23689 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23689 gcc47-pr48163-1.patch Fix for the expand_debug_expr issue. I was very much surprised that for data.passed_pointer parameters (those aren't DECL_BY_REFERENCE) DECL_INCOMING_RTL doesn't reflect where it actually is passed and there is no way to find the fact that it is pass_by_reference (except for repeating all the cumulative args/etc. stuff done by function.c). Either we could use some flag on the PARM_DECL to say this, but I think it is much better to just adjust DECL_INCOMING_RTL in that case. With the additional dwarf2out.c change, e.g. on powerpc-linux (32-bit) we are now able to emit locations for: struct S { char buf[16]; }; void foo (struct S a, int b, int c, int d, int e, int f, int g, int h, struct S i) { } even for a and i parameters, which is something we weren't able to do before.
next prev parent reply other threads:[~2011-03-17 12:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-17 6:20 [Bug regression/48163] New: " hp at gcc dot gnu.org 2011-03-17 9:55 ` [Bug regression/48163] " rguenth at gcc dot gnu.org 2011-03-17 12:07 ` jakub at gcc dot gnu.org [this message] 2011-03-17 12:35 ` [Bug debug/48163] " jakub at gcc dot gnu.org 2011-03-17 20:35 ` jakub at gcc dot gnu.org 2011-03-17 20:41 ` jakub at gcc dot gnu.org 2011-03-17 21:08 ` jakub at gcc dot gnu.org 2011-03-18 2:49 ` hp at gcc dot gnu.org 2013-06-10 18:19 ` ebotcazou 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-48163-4-cUqbLFL6sZ@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).