public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Eric Botcazou" <ebotcazou@libertysurf.fr>
To: "Nathan Froyd" <froydnj@codesourcery.com>, 	<gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] output INCOMING_RETURN_ADDR_RTX in debug info
Date: Sun, 05 Aug 2007 07:13:00 -0000	[thread overview]
Message-ID: <036601c7d730$182ccde0$0a00000a@galilee> (raw)
In-Reply-To: <20070803155148.GA6839@sparrowhawk.codesourcery.com>

> I don't see a reason to make this information conditional on
> DWARF2_UNWIND_INFO--but I am also not a debug info expert.

Yes, the condition is now too weak.

> Clarifications/corrections welcome!

See http://gcc.gnu.org/ml/gcc/2007-04/msg00671.html for another solution.

--
Eric Botcazou

  reply	other threads:[~2007-08-05  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 15:51 Nathan Froyd
2007-08-05  7:13 ` Eric Botcazou [this message]
2007-08-09 15:25   ` Nathan Froyd

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='036601c7d730$182ccde0$0a00000a@galilee' \
    --to=ebotcazou@libertysurf.fr \
    --cc=froydnj@codesourcery.com \
    --cc=gcc-patches@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).