From: Keith Bennett <kanezor@gmail.com>
To: overseers <overseers@gcc.gnu.org>
Subject: GCC bug reporting
Date: Wed, 17 Dec 2014 23:00:00 -0000 [thread overview]
Message-ID: <CAObQs2H95iKYnNDWUDgtwpVW7ZSk-7xxv+_fr_UTxg_N5DFmAQ@mail.gmail.com> (raw)
I am trying to look into what I feel is a deficiency in GCC 4.9.2. Do
I need to create an account on the bugtracker to do this?
What mailing lists do you suggest I ask first about the issue?
--
Keith Bennett
next reply other threads:[~2014-12-16 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 23:00 Keith Bennett [this message]
2016-08-05 1:48 Vladimir Panteleev
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=CAObQs2H95iKYnNDWUDgtwpVW7ZSk-7xxv+_fr_UTxg_N5DFmAQ@mail.gmail.com \
--to=kanezor@gmail.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).