From: Katsunori Kumatani <katsunori.kumatani@gmail.com>
To: overseers@gcc.gnu.org
Subject: Help Creating GCC Bugzilla Account
Date: Wed, 15 Feb 2017 13:08:00 -0000 [thread overview]
Message-ID: <CAH0Jp5HN+=J5ORjTbQHwOcFtxjeNxGLZPo8xHWYxAqzRpYu3EQ@mail.gmail.com> (raw)
Hello, I try once more to contact you for an account for GCC Bugzilla.
I wish to report a regression leading to wrong code generation since
GCC 6 in the use of __restrict__ pointers with inline asms. I've
posted on the mailing list, but I don't think that is ideal, I can't
post on Bugzilla because I cannot create an account.
Thank you.
reply other threads:[~2017-02-15 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAH0Jp5HN+=J5ORjTbQHwOcFtxjeNxGLZPo8xHWYxAqzRpYu3EQ@mail.gmail.com' \
--to=katsunori.kumatani@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).