public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dickrp at ece dot northwestern dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/14521] Inconsistent quoting in new warning
Date: Thu, 11 Mar 2004 05:31:00 -0000 [thread overview]
Message-ID: <20040311053102.587.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040311052610.14521.dickrp@ece.northwestern.edu>
------- Additional Comments From dickrp at ece dot northwestern dot edu 2004-03-11 05:30 -------
The inlining warnings are inconsistent with other diagnostic messages.
Normally, quoting is done like `this'. In the inlining warnings, it is done
like 'this'. This complicates build automation scripts.
Example:
RVector.cct:4: warning: inlining failed in call to 'T&
rstd::RVector<T>::operator[](long int) [with T = rstd::RawGraph::edge_index]':
--param large-function-growth limit reached while inlining the caller
Graph.cc:19: warning: called from here
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14521
next prev parent reply other threads:[~2004-03-11 5:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 5:26 [Bug c++/14521] New: " dickrp at ece dot northwestern dot edu
2004-03-11 5:31 ` dickrp at ece dot northwestern dot edu [this message]
2004-03-11 5:54 ` [Bug middle-end/14521] " pinskia at gcc dot gnu dot org
2004-03-11 9:53 ` jsm at polyomino dot org dot uk
2004-10-31 21:58 ` cvs-commit at gcc dot gnu dot org
2004-10-31 22:04 ` roger at eyesopen dot com
2004-10-31 22:06 ` pinskia at gcc dot gnu dot org
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=20040311053102.587.qmail@sources.redhat.com \
--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).