public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/24432] [4.1 regression] Missing symbols
Date: Tue, 18 Oct 2005 21:43:00 -0000 [thread overview]
Message-ID: <20051018214305.24642.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24432-226@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from fxcoudert at gmail dot com 2005-10-18 21:43 -------
(In reply to comment #0)
> has introduced a bunch of regressions on non-C99 SPARC/Solaris platforms
How come they I don't see those on my sparc-solaris2.9 builds? See
http://quatramaran.ens.fr/~coudert/gfortran/test-results/test-sparc-solaris-20051012.log
and older.
This is particularly annoying, since sparc-solaris2.9 is one of the platforms
on which I regtested this patch!
Other than that, I concur in diagnosis and solution. Will implement that as
soon as possible (most probably on Wednesday evening, European time).
> [FX, please make sure your email address as recorded in the ChangeLog file is
> registered with Bugzilla; same for fxcoudert@gcc.gnu.org. Thanks in advance.]
Sorry, I didn't know that rule. Will use my gcc.gnu.org address in changelogs
in the future. Does that need to be retroactive?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24432
next prev parent reply other threads:[~2005-10-18 21:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 17:22 [Bug libfortran/24432] New: " ebotcazou at gcc dot gnu dot org
2005-10-18 18:05 ` [Bug libfortran/24432] " pinskia at gcc dot gnu dot org
2005-10-18 21:43 ` fxcoudert at gmail dot com [this message]
2005-10-18 21:59 ` ebotcazou at gcc dot gnu dot org
2005-10-18 22:09 ` gdr at integrable-solutions dot net
2005-10-19 8:23 ` cvs-commit at gcc dot gnu dot org
2005-10-19 8:27 ` fxcoudert at gmail dot com
2005-10-19 9:09 ` ebotcazou at gcc dot gnu dot org
2005-10-19 9:45 ` cvs-commit at gcc dot gnu dot org
2005-10-19 9:46 ` fxcoudert at gmail dot com
2005-10-19 14:23 ` ebotcazou at gcc dot gnu dot org
2005-10-19 14:59 ` kargl at gcc dot gnu dot org
2005-10-19 15:09 ` ebotcazou at gcc dot gnu dot org
2005-10-19 17:34 ` kargl at gcc dot gnu dot org
2005-10-19 18:19 ` ebotcazou at gcc dot gnu dot org
2005-10-23 22:54 ` pinskia at gcc dot gnu dot org
2005-11-21 11:45 ` ebotcazou at gcc dot gnu dot org
2005-11-21 12:04 ` fxcoudert at gcc dot gnu dot org
2005-11-21 14:06 ` ebotcazou at gcc dot gnu dot org
2005-11-21 20:52 ` ebotcazou at gcc dot gnu dot org
2005-11-21 20:53 ` ebotcazou at gcc dot gnu dot 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=20051018214305.24642.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).