From: Eli Zaretskii <eliz@gnu.org>
To: Paul Schlie <schlie@comcast.net>
Cc: manjo@austin.ibm.com, m.m.kettenis@alumnus.utwente.nl,
gdb-patches@sources.redhat.com
Subject: Re: [RFC] solib-svr4.c gdb_byteised.
Date: Tue, 31 May 2005 22:22:00 -0000 [thread overview]
Message-ID: <ur7fn9lb7.fsf@gnu.org> (raw)
In-Reply-To: <BEC203C4.A531%schlie@comcast.net> (message from Paul Schlie on Tue, 31 May 2005 12:06:28 -0400)
> Date: Tue, 31 May 2005 12:06:28 -0400
> From: Paul Schlie <schlie@comcast.net>
>
> arguably it seems that the best remedy would be to correct GCC, not attempt
> to appease it
I'm with you on this one, but somehow I doubt you will be able to
convince the GCC maintainers. It's worth a try nonetheless.
next prev parent reply other threads:[~2005-05-31 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 20:45 Paul Schlie
2005-05-31 22:22 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 22:50 Manoj Iyer
2005-05-27 4:41 ` M.M. Kettenis
2005-05-27 4:54 ` Manoj Iyer
2005-05-31 16:06 ` Manoj Iyer
2005-06-03 21:09 ` Kevin Buettner
2005-06-12 0:04 ` Mark Kettenis
2005-06-03 21:14 ` Kevin Buettner
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=ur7fn9lb7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=m.m.kettenis@alumnus.utwente.nl \
--cc=manjo@austin.ibm.com \
--cc=schlie@comcast.net \
/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