public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/30406] ICE in LOGICAL(8) functions
Date: Sat, 10 Feb 2007 22:12:00 -0000 [thread overview]
Message-ID: <20070210221226.16520.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30406-12313@http.gcc.gnu.org/bugzilla/>
------- Comment #30 from dominiq at lps dot ens dot fr 2007-02-10 22:12 -------
Subject: Re: ICE in LOGICAL(8) functions
Francois-Xavier,
Thanks for the work. In order to improve future contributions,
I have a few questions:
(1) do you need a regtesting of the patch on 4.2 and OSX 10.4?
Will 4.2.0 20070124 good enough or should I upgrade to a more
recent version?
(2) > Patches in PR tend to not get reviewed, so we need people
> to post them to the list.
Does this mean, that when I fill a PR, I should put
fortran@gcc.gnu.org in the cc list?
(3) Can people like me post on gcc-patches@gcc.gnu.org?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30406
next prev parent reply other threads:[~2007-02-10 22:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 13:03 [Bug fortran/30406] New: " dominiq at lps dot ens dot fr
2007-01-08 13:33 ` [Bug fortran/30406] " burnus at gcc dot gnu dot org
2007-01-08 13:42 ` dominiq at lps dot ens dot fr
2007-01-08 17:38 ` kargl at gcc dot gnu dot org
2007-01-08 17:44 ` pinskia at gcc dot gnu dot org
2007-01-08 19:05 ` dominiq at lps dot ens dot fr
2007-01-08 20:19 ` dominiq at lps dot ens dot fr
2007-01-08 20:34 ` sgk at troutmask dot apl dot washington dot edu
2007-01-08 20:49 ` dominiq at lps dot ens dot fr
2007-01-09 16:13 ` fxcoudert at gcc dot gnu dot org
2007-01-09 22:06 ` dominiq at lps dot ens dot fr
2007-01-09 22:08 ` pinskia at gcc dot gnu dot org
2007-01-09 22:11 ` dominiq at lps dot ens dot fr
2007-01-10 6:44 ` fxcoudert at gcc dot gnu dot org
2007-01-10 8:11 ` fxcoudert at gcc dot gnu dot org
2007-01-10 9:07 ` pinskia at gcc dot gnu dot org
2007-01-10 22:51 ` pinskia at gcc dot gnu dot org
2007-01-10 22:56 ` pinskia at gcc dot gnu dot org
2007-01-10 23:02 ` [Bug target/30406] " pinskia at gcc dot gnu dot org
2007-01-10 23:04 ` pinskia at gcc dot gnu dot org
2007-01-10 23:04 ` pinskia at gcc dot gnu dot org
2007-01-10 23:09 ` pinskia at gcc dot gnu dot org
2007-01-10 23:20 ` pinskia at gcc dot gnu dot org
2007-01-11 8:08 ` fxcoudert at gcc dot gnu dot org
2007-01-13 17:09 ` dominiq at lps dot ens dot fr
2007-01-29 15:13 ` dominiq at lps dot ens dot fr
2007-01-29 15:31 ` fxcoudert at gcc dot gnu dot org
2007-01-29 17:58 ` pinskia at gcc dot gnu dot org
2007-01-29 20:47 ` dominiq at lps dot ens dot fr
2007-02-10 17:24 ` fxcoudert at gcc dot gnu dot org
2007-02-10 22:12 ` dominiq at lps dot ens dot fr [this message]
2007-02-10 22:21 ` fxcoudert at gcc dot gnu dot org
2007-02-10 22:42 ` pinskia at gcc dot gnu dot org
2007-02-10 22:44 ` dominiq at lps dot ens dot fr
2007-02-13 19:05 ` fxcoudert at gcc dot gnu dot org
2007-03-04 8:10 ` fxcoudert at gcc dot gnu dot org
2007-03-04 8:11 ` [Bug target/30406] [4.1/4.2 only] " fxcoudert at gcc dot gnu dot org
2007-03-05 3:28 ` mmitchel at gcc dot gnu dot org
2007-03-08 12:35 ` fxcoudert at gcc dot gnu dot org
2007-03-08 13:24 ` [Bug target/30406] [4.1 " burnus at gcc dot gnu dot org
2007-03-08 13:34 ` fxcoudert 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=20070210221226.16520.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).