public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/35441] [4.5/4.6/4.7/4.8 regression] Completely broken diagnostics
Date: Sat, 21 Apr 2012 14:55:00 -0000	[thread overview]
Message-ID: <bug-35441-4-jimkGMfZGU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-35441-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35441

--- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-21 14:53:25 UTC ---
Author: manu
Date: Sat Apr 21 14:53:21 2012
New Revision: 186652

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=186652
Log:
2012-04-21  Manuel López-Ibáñez  <manu@gcc.gnu.org>

    PR 35441
    * c-typeck.c (inform_declaration): New.
    (build_function_call_vec):  Do not pretty-print
    expressions when caret is enabled.
    (convert_arguments): Use inform_declaration.
cp/
    * typeck.c (cp_build_function_call_vec): Do not pretty-print
    expressions when caret is enabled.
testsuite/
    * c-c++-common/pr35441.C: New.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/c-typeck.c
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/typeck.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-04-21 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-35441-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 15:00 ` [Bug c/35441] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-03-13 15:29 ` [Bug c/35441] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-04-21 14:55 ` manu at gcc dot gnu.org [this message]
2012-04-21 15:04 ` [Bug c/35441] pretty-printer cannot handle some expressions manu at gcc dot gnu.org
2012-07-02 12:43 ` rguenth at gcc dot gnu.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=bug-35441-4-jimkGMfZGU@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).