From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb-patches@sources.redhat.com, kettenis@chello.nl
Subject: Re: [PATCH] Deal with GCC bug on 64-bit SPARC
Date: Sat, 03 Jan 2004 22:47:00 -0000 [thread overview]
Message-ID: <20040103224717.CBDD04B35A@berman.michael-chastain.com> (raw)
> GCC generates code that doesn't conform to the ABI.
I hate it when that happens.
Can you enhance your comment to say which version of gcc?
gcc 3.4 has a different default ABI than gcc 3.3.
Michael C
next reply other threads:[~2004-01-03 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 22:47 Michael Elizabeth Chastain [this message]
2004-01-03 23:00 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
2004-01-03 23:06 Michael Elizabeth Chastain
2004-01-03 23:34 ` Mark Kettenis
2004-01-03 20:46 Mark Kettenis
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=20040103224717.CBDD04B35A@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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