public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
	    Steve Kargl <sgk@troutmask.apl.washington.edu>,
	    Fortran List <fortran@gcc.gnu.org>, FX <fxcoudert@gmail.com>,
	    gcc@gcc.gnu.org
Subject: Re: For testing: full __float128 patch
Date: Mon, 30 Aug 2010 17:34:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1008301646460.23876@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1008301439150.17560@acrux.dbai.tuwien.ac.at>

On Mon, 30 Aug 2010, Gerald Pfeifer wrote:

> On Mon, 30 Aug 2010, Gerald Pfeifer wrote:
> >> Can you please regression test these two patches on freebsd (32 and 64 
> >> bit)?
> > Tests running...
> 
> Looks like a nice improvement, actually.  On both this fixes previously
> existing test failures and adds some passes (no changes on the failure
> side on i386).
> 
> From all I can tell, please go ahead, Uros. :-)  I wonder whether these
> might also be suitable for GCC 4.5?

Assuming that symbol versioning is enabled on FreeBSD, you need to set 
appropriate versions for all the new symbols in libgcc_s - which would be 
GCC_4.6.0 for something going on trunk only but GCC_4.5.2 for something 
going on 4.5 as well (and with the right %inherit settings in any case).

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2010-08-30 16:48 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 [this message]
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
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=Pine.LNX.4.64.1008301646460.23876@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=sgk@troutmask.apl.washington.edu \
    --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).