From: Joseph Myers <joseph@codesourcery.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: <overseers@gcc.gnu.org>
Subject: Re: gcc x64 linux code generation (passing pointer var-args) bug
Date: Sat, 24 Jan 2015 22:52:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1501242248280.8829@digraph.polyomino.org.uk> (raw)
In-Reply-To: <m38ugr6cgn.fsf@pepe.airs.com>
On Sat, 24 Jan 2015, Ian Lance Taylor wrote:
> Reuben Hawkins <reubenhwk@gmail.com> writes:
>
> > I ran into an issue with all versions of gcc which support x64 which
> > *could* be considered a bug. At the very least, it's a pitfall. I'm
> > not really sure to whom I should bring this problem to. Bugzilla?
> > Mailing list? Not sure...
>
> The overseers mailing list is not the right place. This mailing list is
> for discussion of the maintenance of the systems gcc.gnu.org and
> sourceware.org. You should take this to the mailing list
> gcc-help@gcc.gnu.org. Thanks.
I think we're getting bug reports on overseers because the message about
Bugzilla account creation being restricted points to overseers.
I think the message ought to include more information, such as (a) that
account creation has been restricted because of large amounts of spam, (b)
contact overseers and someone will create an account manually for you (not
"for information about creating an account"), (c) the account will
probably be created within time X, ((d) (if needed) make clear whether
it's GCC Bugzilla or Sourceware Bugzilla you want an account on).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2015-01-24 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 21:36 Reuben Hawkins
2015-01-23 21:40 ` Andrew Pinski
2015-01-23 22:11 ` Reuben Hawkins
2015-01-24 22:28 ` Ian Lance Taylor
2015-01-24 22:52 ` Joseph Myers [this message]
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=alpine.DEB.2.10.1501242248280.8829@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=ian@airs.com \
--cc=overseers@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).