public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/47802] [4.6 Regression] libgfortran/intrinsics/ctime.c:75:3: error: too few arguments to function 'ctime_r'
Date: Wed, 02 Mar 2011 13:58:00 -0000 [thread overview]
Message-ID: <bug-47802-4-HxKnKHyVOO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47802-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47802
--- Comment #28 from Jeffrey A. Law <law at redhat dot com> 2011-03-02 13:58:19 UTC ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/02/11 06:51, jakub at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47802
>
> Jakub Jelinek <jakub at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Priority|P2 |P4
>
> --- Comment #27 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-02 13:51:36 UTC ---
> This isn't a bootstrap failure any longer from what I can understand, any
> Fortran isn't release critical.
And the PA isn't (or shouldn't be) a primary platform :-)
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNbkzwAAoJEBRtltQi2kC70GMH/0ZIq10zhwuOjnMBJaUPMZVV
Bq8Jsu7PqFFE4IJ0rQUpFEcNNmKkPlrINHK3eZNafKTmacqwSfVCZd1worUdvHpH
JRr86cOxHKF2diwih4NpGgx4JtcfeGEDlA5I++3iTRifz5H/nQfrBil7BVI4ocpi
wBcd6mCQa25LxfJePxxR6Az0fDcxxHPnHuQt/ve40v1zugDpk8TE3kjxLXfoclCg
DZIqNZ84D7UGwPuGo/+VYNi07u1RO/MxBStSBFJvCDatAIQ8kzKLP60SVUGfSHyK
auckyBMr5+LQWmJyh50UJyxtYn7c/aLnUzQfQ3aNUNdlaJT1mubgXCgFhzTGw4A=
=pWH0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-02 13:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 16:53 [Bug libfortran/47802] New: " danglin at gcc dot gnu.org
2011-02-18 17:07 ` [Bug libfortran/47802] [4.6 Regression] " burnus at gcc dot gnu.org
2011-02-18 19:55 ` law at redhat dot com
2011-02-18 20:16 ` law at redhat dot com
2011-02-18 21:13 ` dave at hiauly1 dot hia.nrc.ca
2011-02-19 17:30 ` jb at gcc dot gnu.org
2011-02-19 17:31 ` danglin at gcc dot gnu.org
2011-02-19 17:49 ` danglin at gcc dot gnu.org
2011-02-21 17:05 ` law at redhat dot com
2011-02-21 17:43 ` jakub at gcc dot gnu.org
2011-02-21 18:49 ` burnus at gcc dot gnu.org
2011-02-21 18:51 ` law at redhat dot com
2011-02-21 18:53 ` law at redhat dot com
2011-02-21 19:10 ` jakub at gcc dot gnu.org
2011-02-21 19:47 ` dave at hiauly1 dot hia.nrc.ca
2011-02-22 9:31 ` jb at gcc dot gnu.org
2011-02-22 9:36 ` jakub at gcc dot gnu.org
2011-02-22 16:41 ` jb at gcc dot gnu.org
2011-02-22 20:44 ` jb at gcc dot gnu.org
2011-02-23 14:30 ` dave at hiauly1 dot hia.nrc.ca
2011-02-23 14:35 ` dave at hiauly1 dot hia.nrc.ca
2011-02-23 18:32 ` burnus at gcc dot gnu.org
2011-02-23 20:55 ` dave at hiauly1 dot hia.nrc.ca
2011-02-24 12:52 ` jb at gcc dot gnu.org
2011-02-24 14:56 ` jb at gcc dot gnu.org
2011-02-24 15:05 ` dave at hiauly1 dot hia.nrc.ca
2011-02-24 21:54 ` jb at gcc dot gnu.org
2011-02-25 10:58 ` burnus at gcc dot gnu.org
2011-02-26 14:05 ` dave at hiauly1 dot hia.nrc.ca
2011-03-02 13:52 ` jakub at gcc dot gnu.org
2011-03-02 13:58 ` law at redhat dot com [this message]
2011-03-02 14:01 ` jakub at gcc dot gnu.org
2011-03-03 13:57 ` dave at hiauly1 dot hia.nrc.ca
2011-03-04 17:37 ` jb at gcc dot gnu.org
2011-03-04 17:53 ` jb at gcc dot gnu.org
2011-03-04 19:08 ` jb at gcc dot gnu.org
2011-03-04 19:15 ` jb at gcc dot gnu.org
2011-03-05 17:06 ` dave at hiauly1 dot hia.nrc.ca
2011-03-09 7:48 ` jb at gcc dot gnu.org
2011-03-09 13:42 ` burnus at gcc dot gnu.org
2011-03-10 16:59 ` dave at hiauly1 dot hia.nrc.ca
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=bug-47802-4-HxKnKHyVOO@http.gcc.gnu.org/bugzilla/ \
--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).