This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Remove -fexceptions configure test
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Thu, 15 Oct 2015 14:58:13 -0700 (PDT)
- Subject: Re: Remove -fexceptions configure test
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1510152146440 dot 6002 at digraph dot polyomino dot org dot uk>
It sure would be nice if places using special compiler flags for
specific files said why they are doing what they are doing. The
uses-callbacks variable is a nice implicit documentation for the
cases it's used in. Yet we have a few instances that use
"$(uses-callbacks) -fexceptions". This is redundant--but not
completely obviously so, because there is no explanation for
-fexceptions there.
What is the reason for -fexceptions in all those other places? If
each is actually a uses-callbacks case, then we should use that
variable to clarify that in the documentation. I think that's the
actual case for all the stdio cases, because they can lead to
callbacks via _IO_JUMPS.
Do we have any -fexceptions cases that are not actually uses-callbacks?