public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	        GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: when (not) use bugzilla for GCC?
Date: Mon, 26 Oct 2009 14:39:00 -0000	[thread overview]
Message-ID: <mcrfx96s1b9.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <4AE54B94.3090708@starynkevitch.net> (Basile STARYNKEVITCH's message of "Mon\, 26 Oct 2009 08\:11\:16 +0100")

Basile STARYNKEVITCH <basile@starynkevitch.net> writes:

> Are you suggesting me to upload to bugzilla the nearly 3000
> preprocessed forms of the files? I could do that, but the *.i files
> totalize more than one gigabyte. A bzip2 compressed tar archive of
> them is almost 80Mbytes.

That is a difficulty, but without a self-contained test case it's
pretty hard to fix the bug.  You can try reporting the bug with a URL
for where to download the sources.  Since LTO is fairly new a
maintainer may be willing to download them and try it.  Otherwise, go
ahead and upload that 80M tar ball.  gcc.gnu.org will cope.


> Did I understand correctly that GCC bugzilla treats magically the
> *@gcc.gnu.org email adresses matching accounts usable for SVN write
> access? This is great news!

Yes, that is how it works.

Ian

  reply	other threads:[~2009-10-26 14:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 18:48 Basile STARYNKEVITCH
2009-10-26  7:11 ` Joseph S. Myers
2009-10-26 11:57   ` Basile STARYNKEVITCH
2009-10-26 14:39     ` Ian Lance Taylor [this message]
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=mcrfx96s1b9.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
    --to=iant@google.com \
    --cc=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    /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).