From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Subject: Re: libc divdi3 and libgcc
Date: Sat, 03 May 2003 02:30:00 -0000 [thread overview]
Message-ID: <20030502193011.A25601@lucon.org> (raw)
In-Reply-To: <20030503015247.GM924@bubble.sa.bigpond.net.au>; from amodra@bigpond.net.au on Sat, May 03, 2003 at 11:22:47AM +0930
On Sat, May 03, 2003 at 11:22:47AM +0930, Alan Modra wrote:
> On Fri, May 02, 2003 at 08:44:30AM -0700, H. J. Lu wrote:
> > in my binutils. If you still have this problem, please create a small
> > testcase. I will look into it.
>
I see it now. It is odd that I have no problem with gcc on RedHat 9.
I will fix it this weekend.
H.J.
next prev parent reply other threads:[~2003-05-03 2:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 10:12 Alan Modra
2003-05-02 14:39 ` H. J. Lu
2003-05-02 15:44 ` H. J. Lu
2003-05-03 1:52 ` Alan Modra
2003-05-03 2:30 ` H. J. Lu [this message]
2003-05-03 7:06 ` H. J. Lu
2003-05-05 0:30 ` Alan Modra
2003-05-05 0:55 ` H. J. Lu
2003-05-03 16:54 ` H. J. Lu
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=20030502193011.A25601@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.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).