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++/56725] extra spaces in error message
Date: Wed, 27 Mar 2013 17:43:00 -0000	[thread overview]
Message-ID: <bug-56725-4-ub00bhz5YZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56725-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2013-03-27 17:43:02 UTC ---
(In reply to comment #4)
> Hi Manuel. I wanted to actually handle this per your indications and move on,
> but I don't understand why you check the return value of permerror: shouldn't
> we emit the inform anyway, either for an error or a warning?

permerrors can be totally hidden by using "-fpermissive -w" no? (I haven't
actually tested it, so maybe I am wrong). If so, it would be weird to give the
note.
>From gcc-bugs-return-418596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Mar 27 17:48:21 2013
Return-Path: <gcc-bugs-return-418596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13653 invoked by alias); 27 Mar 2013 17:48:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13497 invoked by uid 48); 27 Mar 2013 17:48:14 -0000
From: "pageexec at freemail dot hu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/56754] New: some missing plugin headers during installation in gcc 4.8
Date: Wed, 27 Mar 2013 17:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: plugins
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pageexec at freemail dot hu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-56754-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
X-SW-Source: 2013-03/txt/msg02037.txt.bz2
Content-length: 997


http://gcc.gnu.org/bugzilla/show_bug.cgi?idV754

             Bug #: 56754
           Summary: some missing plugin headers during installation in gcc
                    4.8
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: plugins
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: pageexec@freemail.hu


it used to be the case before 4.8 that the following files were made available
to plugins:

 target.h
 target.def
 target-hooks-macros.h

now it seems that at least for a x86_64-pc-linux-gnu target they no longer get
installed. i tried to find the related commit but came up empty so i'm
wondering if this is the result of an oversight or some policy change? manually
installing these files gets things back to normal, but it'd be nice to know
what to expect in the future or if it's a bug, fix it for 4.8.1 ;).


  parent reply	other threads:[~2013-03-27 17:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-56725-4@http.gcc.gnu.org/bugzilla/>
2013-03-25 23:03 ` manu at gcc dot gnu.org
2013-03-27 15:36 ` paolo.carlini at oracle dot com
2013-03-27 17:43 ` manu at gcc dot gnu.org [this message]
2013-03-27 19:28 ` paolo.carlini at oracle dot com
2013-03-27 19:47 ` manu at gcc dot gnu.org
2013-03-27 20:24 ` manu at gcc dot gnu.org
2013-03-27 20:37 ` manu at gcc dot gnu.org
2013-03-28 16:06 ` paolo.carlini at oracle dot com

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-56725-4-ub00bhz5YZ@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).