From: James E Wilson <wilson@specifixinc.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com
Subject: Re: PATCH: Add -munwind-check=[none|warning|error]
Date: Fri, 11 Feb 2005 23:49:00 -0000 [thread overview]
Message-ID: <1108154508.19527.47.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <20050211190009.GA6759@lucon.org>
On Fri, 2005-02-11 at 11:00, H. J. Lu wrote:
> > Here is the new patch. I removed the -munwind-check=none option. I also
> > included the patch for the .endp check. IAS does ignore the name
> > after .endp. But checking it is a good idea. People will get a
> > warning unless they fix the code.
In case I wasn't clear, I am not opposed to having the
-munwind-check=none option, just to the amount of ugly code that was
used to implement it in the previous patch. I think it would be foolish
to disable these checks now that we have them, but I can see that there
might be unusual cases where this might be useful.
About the .endp patch, I needed to take a closer look at that one as it
confused me. Jan's comment said to change default name from NULL to ""
to avoid a segfault, you thanked him for the bug report, but you didn't
change this. And since I apparently didn't receive either your original
patch or Jan's reply to it, it wasn't clear to me whether the problem
was still broken or had been fixed a different way.
I now suspect it was fixed a different way by adding the "&&
default_name" line, as I don't see a problem.
> * NEWS: Mention "-munwind-check=[warning|error]".
> * config/tc-ia64.c (md): Add unwind_check.
> (unwind_diagnostic): New.
> ...
OK.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2005-02-11 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 23:31 H. J. Lu
2005-02-11 10:55 ` James E Wilson
2005-02-11 20:02 ` H. J. Lu
2005-02-11 20:20 ` H. J. Lu
2005-02-11 23:49 ` James E Wilson [this message]
2005-02-12 6:28 ` H. J. Lu
2005-02-13 10:56 ` James E Wilson
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=1108154508.19527.47.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.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).