From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Richard Henderson <rth@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Gerald Pfeifer <gerald@pfeifer.com>,
Fortran List <fortran@gcc.gnu.org>,
FX <fxcoudert@gmail.com>,
gcc@gcc.gnu.org
Subject: Re: For testing: full __float128 patch
Date: Tue, 31 Aug 2010 04:32:00 -0000 [thread overview]
Message-ID: <20100830222920.GA95778@troutmask.apl.washington.edu> (raw)
In-Reply-To: <AANLkTin_2oLsetQG1xoziLEeKB3-eWU7oCCCwHwmOwqx@mail.gmail.com>
On Mon, Aug 30, 2010 at 09:51:09PM +0200, Uros Bizjak wrote:
>
> So, attached and untested.
>
> Uros.
I tested your patch on x86_64-*-freebsd. My ppl and cloog
libraries were built with FreeBSD's system gcc (4.2.1). All
tests failed due to missing symbols that are marked GCC_3.0.
> Index: gcc/config/i386/t-freebsd
> ===================================================================
> --- gcc/config/i386/t-freebsd (revision 0)
> +++ gcc/config/i386/t-freebsd (revision 0)
> @@ -0,0 +1 @@
> +SHLIB_MAPFILES = $(srcdir)/config/i386/libgcc-bsd.ver
Changing the = to += seems to fix the problem. My
regression testing is still running, so I can't
report stats.
--
Steve
next prev parent reply other threads:[~2010-08-30 22:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 1:55 Uros Bizjak
2010-08-30 1:59 ` Steve Kargl
2010-08-30 7:42 ` Uros Bizjak
2010-08-30 10:46 ` Gerald Pfeifer
2010-08-30 16:48 ` Gerald Pfeifer
2010-08-30 17:34 ` Joseph S. Myers
2010-08-30 17:43 ` Uros Bizjak
2010-08-30 18:27 ` Richard Henderson
2010-08-30 19:25 ` Uros Bizjak
2010-08-30 19:38 ` Uros Bizjak
2010-08-30 19:51 ` Richard Henderson
2010-08-30 19:54 ` Jakub Jelinek
2010-08-30 22:29 ` Uros Bizjak
2010-08-31 4:32 ` Steve Kargl [this message]
2010-08-31 7:10 ` Steve Kargl
2010-08-31 3:37 ` Joseph S. Myers
2010-08-30 17:37 ` Steve Kargl
-- strict thread matches above, loose matches on Subject: below --
2010-08-29 0:57 FX
2010-08-29 1:48 ` Steve Kargl
2010-08-29 7:03 ` Steve Kargl
2010-08-29 11:43 ` Steve Kargl
2010-08-29 12:02 ` FX
2010-08-29 20:48 ` Steve Kargl
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=20100830222920.GA95778@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=rth@redhat.com \
--cc=ubizjak@gmail.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).