From: Uros Bizjak <ubizjak@gmail.com>
To: Richard Henderson <rth@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Gerald Pfeifer <gerald@pfeifer.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 19:38:00 -0000 [thread overview]
Message-ID: <AANLkTi=s=nsN60paQLh7ihLOYETDKCU36Yj5KYChM+pC@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin8MFVkEDmG9nW6PiPiz+i0W=ZXwDORWaqJBYsd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Mon, Aug 30, 2010 at 7:53 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
>>> I'm not familiar in versioning stuff, but since soft-fp symbols are
>>> part of generic libgcc-std.ver for a long time (before 4.5.0), I
>>> believe, it is enough to patch only configure files (see i.e. commits
>>> that enabled soft-fp on mingw/cygwin/-gnu*).
>>
>> It will "work", but not properly. One should never have symbols
>> magically appear in old versions. If you add the symbols to the
>> proper current version number in a config/gcc/i386/libgcc-bsd.ver,
>> they'll appear at the right place.
>
> Can someone please help here?
Attached is my best (untested) shot at libgcc-bsd.ver. Someone has to
write i386/t-freebsd (similar to i386/t-linux) and connect it to the
build system. The versioning assumes that this will be committed to
4.5.x first.
Uros.
[-- Attachment #2: libgcc-bsd.ver --]
[-- Type: application/octet-stream, Size: 1793 bytes --]
# Copyright (C) 2010 Free Software Foundation, Inc.
#
# This file is part of GCC.
#
# GCC is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3, or (at your option)
# any later version.
#
# GCC is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with GCC; see the file COPYING3. If not see
# <http://www.gnu.org/licenses/>.
# 128 bit long double support was introduced with GCC 4.5.0.
# These lines make the symbols to get a @@GCC_4.5.0 attached.
%exclude {
__addtf3
__divtc3
__divtf3
__eqtf2
__extenddftf2
__extendsftf2
__extendxftf2
__fixtfdi
__fixtfsi
__fixtfti
__fixunstfdi
__fixunstfsi
__fixunstfti
__floatditf
__floatsitf
__floattitf
__floatunditf
__floatunsitf
__floatuntitf
__getf2
__gttf2
__letf2
__lttf2
__multc3
__multf3
__negtf2
__netf2
__powitf2
__subtf3
__trunctfdf2
__trunctfsf2
__trunctfxf2
__unordtf2
}
GCC_4.5.0 {
__addtf3
__divtc3
__divtf3
__eqtf2
__extenddftf2
__extendsftf2
__extendxftf2
__fixtfdi
__fixtfsi
__fixunstfdi
__fixunstfsi
__floatditf
__floatsitf
__floattitf
__floatunditf
__floatunsitf
__getf2
__gttf2
__letf2
__lttf2
__multc3
__multf3
__negtf2
__netf2
__powitf2
__subtf3
__trunctfdf2
__trunctfsf2
__trunctfxf2
__unordtf2
}
%ifdef __x86_64__
GCC_4.5.0 {
__fixtfti
__fixunstfti
__floatuntitf
}
%else
GCC_4.5.0 {
__copysigntf3
__fabstf2
}
%endif
next prev parent reply other threads:[~2010-08-30 19:25 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 [this message]
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='AANLkTi=s=nsN60paQLh7ihLOYETDKCU36Yj5KYChM+pC@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=joseph@codesourcery.com \
--cc=rth@redhat.com \
--cc=sgk@troutmask.apl.washington.edu \
/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).