From: Doug Evans <dje@sebabeach.org>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: cgen@sourceware.org
Subject: Re: CGEN_VERBOSE_ASSEMBLER_ERRORS
Date: Tue, 01 Dec 2009 18:04:00 -0000 [thread overview]
Message-ID: <4B155A90.9080705@sebabeach.org> (raw)
In-Reply-To: <4B155D6F.8060103@gmail.com>
Dave Korn wrote:
> Doug Evans wrote:
>
>> Anyone know of a reason why we shouldn't just nuke
>> CGEN_VERBOSE_ASSEMBLER_ERRORS and always have verbose error messages?
>>
>
> Might conceivably cause some minor perturbation in the gas testsuite for any
> target that doesn't currently define it and that has tests of error cases, but
> nothing that can't be easily fixed. Maybe it would be worth pinging the
> binutils list?
>
> cheers,
> DaveK
>
Hi.
I'm not worried about breaking the testsuites. Those things I can find
and fix before checkin. I'm just wondering why it exists at all
(basically). [Other than laziness of updating the testsuites when it
was added. :-)]
prev parent reply other threads:[~2009-12-01 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 9:09 CGEN_VERBOSE_ASSEMBLER_ERRORS Doug Evans
2009-12-01 18:00 ` CGEN_VERBOSE_ASSEMBLER_ERRORS Dave Korn
2009-12-01 18:04 ` Doug Evans [this message]
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=4B155A90.9080705@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@sourceware.org \
--cc=dave.korn.cygwin@googlemail.com \
/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).