From: "\"Jürgen Urban\"" <JuergenUrban@gmx.de>
To: Richard Sandiford <rdsandiford@googlemail.com>, law@redhat.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Support for MIPS r5900
Date: Tue, 08 Jan 2013 22:49:00 -0000 [thread overview]
Message-ID: <20130108224924.27410@gmx.net> (raw)
In-Reply-To: <87mwwk2l6p.fsf@talisman.default>
> > IIRC we defined doubles as 32bits wide in our old port. We simply
> > didn't support 64bit wide doubles. I don't remember what mechanism we
> > used to make this happen.
>
> Ah, yeah.
I think limiting wide doubles would be good.
> >>> I tried to disable dmult and ddiv (see mips.md). Disabling worked, but
> >>> now muldi3 calls itself in libgcc2. I thought this should work,
> because
> >>> I got this working with GCC 4.3, but the latest GCC version is a
> >>> problem. multi3 is calling muldi3, so that muldi3 should be able to
> use
> >>> mulsi3, because it is the same C code in libgcc2. Can someone get me
> >>> some hints or comments? How can this be debugged?
> >>
> >> Not sure, sorry.
> > IIRC I simply disabled muldi3_internal2 and I think we defined away
> > everything related to timode except register-register moves.
@Jeff: I think you know the stringent copyright rules for GCC. I want to use the code from the original patch, but I don't know how many people were involved. So I can't use it without copyright problems. Can you please tell me which code can I use without encountering copyright problems? I plan to submit the code for fixing the r5900 short loop bug in GCC.
> AIUI the problem that Jürgen's hitting is that _muldi3.o
> in libgcc actually contains __multi3 on 64-bit targets,
> because LIBGCC2_UNITS_PER_WORD == 8. Presumably _mulsi3.o would
> then contain __muldi3 where needed, but that file doesn't exist.
> So he was trying to add it.
Yes, this is exactly what happened.
Best regards
Jürgen
next prev parent reply other threads:[~2013-01-08 22:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 22:57 "Jürgen Urban"
2013-01-07 17:15 ` Jeff Law
2013-01-07 20:44 ` Richard Sandiford
2013-01-07 21:52 ` Richard Sandiford
2013-01-08 0:23 ` Maciej W. Rozycki
2013-01-08 7:28 ` Richard Sandiford
2013-01-08 17:24 ` Maciej W. Rozycki
2013-01-08 18:25 ` Richard Sandiford
2013-01-08 22:34 ` "Jürgen Urban"
2013-01-10 23:25 ` Maciej W. Rozycki
2013-01-11 9:49 ` Richard Sandiford
2013-01-11 16:55 ` Maciej W. Rozycki
2013-01-13 14:16 ` "Jürgen Urban"
2013-01-14 18:42 ` Maciej W. Rozycki
2013-01-17 22:21 ` "Jürgen Urban"
2013-01-17 23:23 ` Maciej W. Rozycki
2013-01-19 10:53 ` Richard Sandiford
2013-01-20 21:43 ` "Jürgen Urban"
2013-01-08 4:22 ` Jeff Law
2013-01-08 7:22 ` Richard Sandiford
2013-01-08 22:49 ` "Jürgen Urban" [this message]
2013-01-09 5:25 ` Jeff Law
2013-01-10 22:59 ` "Jürgen Urban"
2013-01-11 4:41 ` Jeff Law
2013-01-08 7:16 ` Richard Sandiford
2013-01-08 21:30 ` "Jürgen Urban"
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=20130108224924.27410@gmx.net \
--to=juergenurban@gmx.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=rdsandiford@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).