From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3] Fix -Os related build and test failures.
Date: Sat, 29 Oct 2016 03:26:00 -0000 [thread overview]
Message-ID: <96997355-530d-98bd-64b4-1d931cd61692@redhat.com> (raw)
In-Reply-To: <db9cd7c1-1f32-8fc9-873d-f13bf563a301@redhat.com>
On 10/28/2016 10:57 PM, Carlos O'Donell wrote:
> OK?
>
> 2016-10-28 Carlos O'Donell <carlos@redhat.com>
>
> [BZ #20729]
> * include/libc-internal.h (DIAG_IGNORE_Os_NEEDS_COMMENT):
> Define.
> * iso-2022-cn-ext.c: Include libc-internal.h and ignore
> -Wmaybe-uninitialized for BODY macro only for -Os compiles.
> * locale/weight.h (findix): Ignore -Wmaybe-uninitialized error
> for seq2.back_us and seq1.back_us only for -Os compiles.
> * locale/weightwc.h (findix): Likewise.
> * nptl_db/thread_dbP.h: Ignore -Wmaybe-uninitialized error for
> DB_GET_FIELD_ADDRESS only for -Os compiles.
> * resolv/res_send (reopen): Ignore -Wmaybe-uninitialized error
> for slen only for -Os compiles.
> * string/strcoll_l.c (get_next_seq): Ignore
> -Wmaybe-uninitialized for seq2.save_idx and seq1.save_idx only
> for -Os compiles.
>
> +/* Similar to DIAG_IGNORE_NEEDS_COMMENT the following macro ignores the
> + diagnostic OPTION but only if optimizations for size are enabled.
> + This is required because different warnings may be generated for
> + different optimization levels. For example a key piece of code may
> + only generate a warning when compiled at -Os, but at -O2 you could
> + still want the warning to be enabled to catch errors. In this case
> + you would use DIAG_IGNORE_Os_NEEDS_COMMENT to disable the warning
> + only for -Os. */
> +#if __OPTIMIZE_SIZE__
> +#define DIAG_IGNORE_Os_NEEDS_COMMENT(version, option) \
> + _Pragma (_DIAG_STR (GCC diagnostic ignored option))
> +#else
> +#define DIAG_IGNORE_Os_NEEDS_COMMENT(version, option)
> +#endif
Typo. s/if/ifdef/g, since __OPTIMIZE_SIZE__ is not defined at -O2.
Fixed.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-10-29 3:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 4:48 [PATCH] Fix -Os related -Werror failures Carlos O'Donell
2016-10-28 6:25 ` Andreas Schwab
2016-10-28 6:32 ` Florian Weimer
2016-10-28 6:44 ` Jeff Law
2016-10-28 8:12 ` Arnd Bergmann
2016-10-28 8:17 ` Andrew Pinski
2016-10-28 13:28 ` Jeff Law
2016-10-28 20:10 ` Paul Eggert
2016-10-29 3:03 ` Jeff Law
2016-10-30 4:25 ` Paul Eggert
2016-10-28 12:09 ` Carlos O'Donell
2016-10-28 12:43 ` Florian Weimer
2016-10-28 13:04 ` Joseph Myers
2016-10-28 13:07 ` Carlos O'Donell
2016-10-28 12:49 ` Joseph Myers
2016-10-28 12:55 ` Florian Weimer
2016-10-28 13:18 ` Carlos O'Donell
2016-10-28 13:58 ` [PATCH v2] Fix -Os related build and test failures Carlos O'Donell
2016-10-28 14:17 ` Joseph Myers
2016-10-29 2:59 ` [PATCH v3] " Carlos O'Donell
2016-10-29 3:26 ` Carlos O'Donell [this message]
2016-10-29 17:35 ` Joseph Myers
2016-10-30 3:51 ` [PATCH v4] " Carlos O'Donell
2016-10-31 8:33 ` Andreas Schwab
2016-10-31 9:16 ` Carlos O'Donell
2016-10-31 9:22 ` Florian Weimer
2016-10-31 12:56 ` David Miller
2016-10-31 19:56 ` Carlos O'Donell
2016-11-01 22:59 ` Joseph Myers
2016-11-02 12:52 ` Carlos O'Donell
2016-11-01 9:17 ` Andreas Schwab
2016-11-01 11:13 ` Joseph Myers
2016-11-01 15:58 ` Tamar Christina
2016-11-01 16:06 ` David Miller
2016-11-01 16:15 ` Tamar Christina
2016-11-02 11:53 ` Carlos O'Donell
2016-11-02 17:03 ` Carlos O'Donell
2016-11-02 13:22 ` Carlos O'Donell
2016-10-31 18:38 ` [PATCH v3] " Steve Ellcey
2016-10-31 19:50 ` Carlos O'Donell
2016-10-31 19:57 ` Steve Ellcey
2016-10-31 20:50 ` Carlos O'Donell
2016-10-31 21:00 ` Steve Ellcey
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=96997355-530d-98bd-64b4-1d931cd61692@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).