From: Mark Kettenis <kettenis@chello.nl>
To: mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: Re: prologue ripper
Date: Sun, 01 Aug 2004 17:10:00 -0000 [thread overview]
Message-ID: <200408011710.i71HAVUM092181@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <410D1A69.nailMDH1AX7PW@mindspring.com> (message from Michael Chastain on Sun, 01 Aug 2004 12:29:29 -0400)
Date: Sun, 01 Aug 2004 12:29:29 -0400
Sender: mec.gnu@mindspring.com
mark> On systems that use the -freg-struct-return by default (FreeBSD,
mark> OpenBSD, Cygwin and a few others) I guess there are a bit more
mark> possibilities.
I don't have a Cygwin, but I have been using FreeBSD and OpenBSD
in the HP Test Drive cluster. I'll just hop on, do some builds,
and prologue-rip them.
Well, FreeBSD and OpenBSD both use older versions of GCC, so you can
probably spend your time doing something useful ;-). I'll cover
FreeBSD and OpenBSD anyway, since that's where I do my development.
prev parent reply other threads:[~2004-08-01 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200408011244.i71CicIt041460@elgar.kettenis.dyndns.org>
2004-08-01 16:29 ` Michael Chastain
2004-08-01 17:10 ` Mark Kettenis [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=200408011710.i71HAVUM092181@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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