public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58944] [4.9 Regression] bogus -Wunused-macros warnings when compiling Libreoffice
Date: Fri, 17 Jan 2014 13:44:00 -0000	[thread overview]
Message-ID: <bug-58944-4-LzNXRl9HXq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58944-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |ASSIGNED
                 CC|                            |jakub at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 31872
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31872&action=edit
gcc49-pr58944.patch

Untested fix.  It makes no sense to warn about these compiler predefined macros
with -Wunused-macros, the user has no control on what GCC predefines and what
it doesn't.  This patch seems to be the easiest hack for this.  rs6000 will
likely need similar change.


  parent reply	other threads:[~2014-01-17 13:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 18:24 [Bug other/58944] New: " octoploid at yandex dot com
2013-10-31 19:06 ` [Bug other/58944] " octoploid at yandex dot com
2013-11-04 20:25 ` tmsriram at google dot com
2013-11-06  1:18 ` tmsriram at google dot com
2013-11-19 10:42 ` [Bug target/58944] " rguenth at gcc dot gnu.org
2013-11-19 17:39 ` tmsriram at google dot com
2013-12-03  3:14 ` tmsriram at gcc dot gnu.org
2013-12-03  3:17 ` tmsriram at google dot com
2013-12-03 13:23 ` octoploid at yandex dot com
2013-12-13 15:02 ` octoploid at yandex dot com
2014-01-17 13:44 ` jakub at gcc dot gnu.org [this message]
2014-01-18 10:19 ` jakub at gcc dot gnu.org
2014-01-18 10:24 ` jakub 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-58944-4-LzNXRl9HXq@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).