public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <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:21:00 -0000 [thread overview] Message-ID: <20070210222107.19461.qmail@sourceware.org> (raw) In-Reply-To: <bug-30406-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #31 from fxcoudert at gcc dot gnu dot org 2007-02-10 22:21 ------- (In reply to comment #30) > (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? It's OK. The change is simple and that part of code (this part of the powerpc backend) hasn't changed for a long time. >> (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? No, otherwise the list will be flooded with bugzilla mail and we will all get lost reading through it. bugzilla PRs are fine because the itemize problems and gather the advances in the investigations in one central place. We don't want everyone's attention spreaded on all the problems, because that would be very inefficient: we want people to pick a task, and go for it, with help of a few others. But, when a patch is designed for a bug, then its needs to be reviewed by a maintainer of the relevant part of the compiler, and approved. This means, it needs to be posted to the gcc-patches mailing-list, because maintainers (although they go through the PRs every now and then) can't keep an eye on all of them. > (3) Can people like me post on gcc-patches@gcc.gnu.org? Anyone who has a patch that he wants reviewed can post it on gcc-patches. Usually, one posts patches of one's own design, but not necessary (as long as the person who designed the patch agrees with it): it can help relieve people who created the patch of some of the administrative burden, like the regtesting. You'll note there are certain contraints on patch submission, to make sure we keep a certain standard in patches and don't waste reviewers' time. Building, regtesting, adding testcases and ChangeLog entries is part of that. You can read a few gcc-patches discussions on the web archives to get a better idea of how it works. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30406
next prev parent reply other threads:[~2007-02-10 22:21 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 2007-02-10 22:21 ` fxcoudert at gcc dot gnu dot org [this message] 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=20070210222107.19461.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: linkBe 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).