public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59522] "cc1plus: error: unrecognized command line option ‘-fmy-loop-block’ " is generated when g++ is run but not with cc1plus
Date: Mon, 16 Dec 2013 09:02:00 -0000 [thread overview]
Message-ID: <bug-59522-4-huSI77al0y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59522-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59522
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #1)
> Bugzilla isn't the right place for these kind of questions, use gcc-help
> mailing list.
Even gcc-help might not be the correct place to ask this question. gcc@ might
be better since this is a question about modifying gcc rather than using gcc.
prev parent reply other threads:[~2013-12-16 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 6:18 [Bug c++/59522] New: " abhilash_bhandari at yahoo dot co.in
2013-12-16 9:01 ` [Bug c++/59522] " pinskia at gcc dot gnu.org
2013-12-16 9:02 ` pinskia at gcc dot gnu.org [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=bug-59522-4-huSI77al0y@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).