From: Mike Frysinger <vapier@gentoo.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: dave.anglin@nrc.ca, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: 64-bit long double support.
Date: Fri, 17 Nov 2006 01:29:44 -0500 [thread overview]
Message-ID: <200611170129.45825.vapier@gentoo.org> (raw)
In-Reply-To: <20061117053556.GA694@hiauly1.hia.nrc.ca>
[-- Attachment #1.1: Type: text/plain, Size: 1096 bytes --]
On Friday 17 November 2006 00:35, John David Anglin wrote:
> > http://gcc.gnu.org/PR29114
>
> This has nothing to do with the discussion about long double support.
i didnt say it does ... i responding to the "testing NPTL in distros" comment
> From the PR, this only occurs in a cross from 64-bit host to 32-bit target.
> There's no 64-bit parisc-linux host...
i said that in my e-mail:
"plus, it makes it hard doing cross-compiles when my 64bit hosts"
> It would appear that the adddi3 expander in pa.md isn't used for some
> reason in the initial code expansion as it would reject the insn. You
> are in the best position to determine where the insn is being emitted from.
> It could be being emitted from the generic code or the PA backend. Try
> breaks on emit_move_sequence, emit_insn, emit_insn_after or
> emit_insn_before and see if you can find where the insn is being emitted.
erm, i've never debugged gcc before ... my experience involves producing
reduced test cases and getting others to verify/fix gcc :)
but if it'll be of help to people ...
-mike
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-11-17 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <119aab440611161731p47779d1hdc7e7dbd336eb23c@mail.gmail.com>
2006-11-17 1:48 ` [parisc-linux] Re: 64-bit long double support John David Anglin
[not found] ` <200611170148.kAH1moG4028180@hiauly1.hia.nrc.ca>
2006-11-17 3:48 ` Carlos O'Donell
2006-11-17 4:10 ` Mike Frysinger
2006-11-17 4:16 ` Mike Frysinger
2006-11-17 4:59 ` Mike Frysinger
2006-11-17 19:16 ` Jeff Bailey
2006-11-17 5:35 ` John David Anglin
2006-11-17 6:29 ` Mike Frysinger [this message]
2006-11-17 16:48 ` John David Anglin
[not found] ` <200611171502.49875.vapier@gentoo.org>
2006-11-17 20:51 ` [parisc-linux] gcc ICE PR29114 (was: 64-bit long double support.) John David Anglin
2006-11-17 21:12 ` Mike Frysinger
2006-11-17 21:16 ` Mike Frysinger
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=200611170129.45825.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=dave.anglin@nrc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.