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 middle-end/48597] x86-64 unwind register save location misses half-register write?
Date: Tue, 03 May 2011 16:37:00 -0000	[thread overview]
Message-ID: <bug-48597-4-0KpZ4LBy2C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48597-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48597

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-03 16:36:02 UTC ---
Author: jakub
Date: Tue May  3 16:35:56 2011
New Revision: 173327

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173327
Log:
    Backport from mainline
    2011-04-28  Jakub Jelinek  <jakub@redhat.com>

    PR middle-end/48597
    * final.c (final_scan_insn): Call dwarf2out_frame_debug even for
    inline asm.

Modified:
    branches/gcc-4_5-branch/gcc/ChangeLog
    branches/gcc-4_5-branch/gcc/final.c


  parent reply	other threads:[~2011-05-03 16:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  0:10 [Bug c/48597] New: " lat at cern dot ch
2011-04-14  7:53 ` [Bug c/48597] " lat at cern dot ch
2011-04-14  8:22 ` jakub at gcc dot gnu.org
2011-04-14  9:23 ` rguenth at gcc dot gnu.org
2011-04-14  9:24 ` jakub at gcc dot gnu.org
2011-04-14 12:02 ` jakub at gcc dot gnu.org
2011-04-14 12:35 ` [Bug middle-end/48597] " jakub at gcc dot gnu.org
2011-04-14 12:38 ` jakub at gcc dot gnu.org
2011-04-15  5:40 ` lat at cern dot ch
2011-04-28 17:11 ` jakub at gcc dot gnu.org
2011-04-28 17:19 ` jakub at gcc dot gnu.org
2011-04-28 17:23 ` jakub at gcc dot gnu.org
2011-05-03 16:37 ` jakub at gcc dot gnu.org [this message]
2011-05-04  9:22 ` 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-48597-4-0KpZ4LBy2C@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).