public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24518] Intrinsic MOD incorrect for large arg1/arg2 and slow.
Date: Sat, 02 Dec 2006 08:12:00 -0000 [thread overview]
Message-ID: <20061202081246.8173.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24518-9236@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from ebotcazou at gcc dot gnu dot org 2006-12-02 08:12 -------
Just to let you know that the Fortran compiler has been broken for about a
month on all Solaris versions (except release 10) with:
Undefined first referenced
symbol in file
fmodf
/opt/build/eric/gcc/sparc64-sun-solaris2.9/.
/libgfortran/.libs/libgfortran.so
fmodl
/opt/build/eric/gcc/sparc64-sun-solaris2.9/.
/libgfortran/.libs/libgfortran.so
ld: fatal: Symbol referencing errors. No output written to ./PR19754_2.exe
collect2: ld returned 1 exit status
compiler exited with status 1
NAME
fmod, fmodf, fmodl - floating-point remainder function
CONFORMING TO
SVID 3, POSIX, BSD 4.3, ISO 9899. The float and the long double vari-
ants are C99 requirements.
Given that you guys regularly break the compiler on non-C99 platforms, I'd
suggest to arrange for having your changes tested on one of them beforehand,
possibly by asking Laurent Guerby of the CompileFarm project to install
an old Linux distro on one of his old machine.
--
ebotcazou at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24518
next prev parent reply other threads:[~2006-12-02 8:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 13:21 [Bug fortran/24518] New: " paul dot richard dot thomas at cea dot fr
2005-10-25 14:37 ` [Bug fortran/24518] " pinskia at gcc dot gnu dot org
2006-06-20 12:44 ` fxcoudert at gcc dot gnu dot org
2006-06-21 8:04 ` paul dot richard dot thomas at cea dot fr
2006-10-22 21:01 ` fxcoudert at gcc dot gnu dot org
2006-10-23 6:19 ` fxcoudert at gcc dot gnu dot org
2006-10-25 7:34 ` uros at kss-loka dot si
2006-10-25 8:19 ` fxcoudert at gcc dot gnu dot org
2006-10-25 11:49 ` uros at kss-loka dot si
2006-10-25 13:53 ` fxcoudert at gcc dot gnu dot org
2006-10-25 14:16 ` uros at kss-loka dot si
2006-10-26 4:04 ` sgk at troutmask dot apl dot washington dot edu
2006-10-26 20:09 ` pault at gcc dot gnu dot org
2006-10-26 22:22 ` uros at kss-loka dot si
2006-10-31 15:56 ` pault at gcc dot gnu dot org
2006-10-31 16:06 ` fxcoudert at gcc dot gnu dot org
2006-10-31 16:14 ` paul dot richard dot thomas at cea dot fr
2006-10-31 16:21 ` pault at gcc dot gnu dot org
2006-10-31 16:47 ` fxcoudert at gcc dot gnu dot org
2006-11-05 6:28 ` pault at gcc dot gnu dot org
2006-11-05 8:46 ` pault at gcc dot gnu dot org
2006-11-05 22:18 ` pault at gcc dot gnu dot org
2006-11-10 21:53 ` pault at gcc dot gnu dot org
2006-12-01 0:09 ` chaoyingfu at gcc dot gnu dot org
2006-12-02 8:12 ` ebotcazou at gcc dot gnu dot org [this message]
2006-12-02 8:23 ` burnus at gcc dot gnu dot org
2006-12-02 8:28 ` pinskia at gcc dot gnu dot org
[not found] <bug-24518-4@http.gcc.gnu.org/bugzilla/>
2012-05-05 8:02 ` jb at gcc dot gnu.org
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=20061202081246.8173.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 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).