public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: GCC Mailing List <gcc@gcc.gnu.org>
Subject: when (not) use bugzilla for GCC?
Date: Sun, 25 Oct 2009 18:48:00 -0000	[thread overview]
Message-ID: <4AE4998D.7040608@starynkevitch.net> (raw)

Hello All,


Please accept my apologies if the questions below are too naive!

I have several questions about bugzilla and GCC. I am not very familiar 
with bugzilla, and I am not familiar with the configuration of GCC 
bugzilla in particular.

I cannot understand when should I use or not bugzilla. More precisely, I 
have several examples of "bugs" but I didn't use bugzilla for them


1. I regularily test the latest gcc trunk with -flto on a medium sized 
program. And it always crashes, with a sisegv fatal error. My feeling is 
that it should not crash that way (at least, I would prefer a message 
such as not enough memory to compile with -flto). Should I report that 
as a bug on bugzilla? I am not able at all to reduce that example to 
something smaller.

For the record, that program is Jacques Pitrat's MALICE system 
http://pagesperso-orange.fr/jacques.pitrat/MALICE.html
about 370KLOC  (less than 14Mbytes total) of C files (all 2947 C files 
are generated and usually short, MALICE is bootstrapped that is 
generates all its C code; the C code is not understandable!). I would 
imagine that it is not big enough to reach the limits of my 8Gb desktop!


Should I report that as a bug?


2. a couple of weeks ago, I submitted a patch regarding gengtype for 
plugins (the patch was greatly improved by Rafael Espindola 
espindola@google.com) and the patch did correct a bug. 
http://gcc.gnu.org/ml/gcc-patches/2009-10/msg00379.html
but I never bothered registering it (since making the initial patch was 
easier than reporting a bug). This is also the case of 
http://gcc.gnu.org/ml/gcc-patches/2009-10/msg00809.html
(fatal error when failing to register a pass)


3. On the MELT branch, I regularily find bugs & correct them, and it did 
happen that someone registered a MELT bug on the bugzilla; I did correct 
it but AFAIR was not permitted to close the bug. Sometimes I am sad of 
not being able to report MELT bugs on bugzilla and to close them when I 
feel I have covered them.





My current intuition is that bugzilla might be reserved for bugs of the 
trunk mostly  for which a small testcase is available, and which is a 
bug affecting many users (this is not the case of all the bugs 
mentionned above).

So when should I use bugzilla? I am a bit "scared" to use it!


I hope I am not offending anyone, and I admit that I am not familiar 
with bugzilla in general and its GCC policy & setting in particular.

I also am guessing that bugzilla is less important for the GCC community 
than in some other big free software communities. It does not seem to be 
a major communication channel.

Regards.
-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

             reply	other threads:[~2009-10-25 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 18:48 Basile STARYNKEVITCH [this message]
2009-10-26  7:11 ` Joseph S. Myers
2009-10-26 11:57   ` Basile STARYNKEVITCH
2009-10-26 14:39     ` Ian Lance Taylor
2009-10-26 14:41       ` Richard Guenther
2009-10-26 14:56         ` Basile STARYNKEVITCH
2009-10-26 15:39           ` Richard Guenther
2009-10-29  5:35           ` Basile STARYNKEVITCH
2009-10-26 20:46       ` Basile STARYNKEVITCH
2009-10-26 21:42         ` Ian Lance Taylor

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=4AE4998D.7040608@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=gcc@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).