With gcc 4.3.4, -Wdisabled-optimization is noisy unless you also
use -funit-at-a-time.
With gcc 4.4.7, there is no indication which warning option
triggered a particular message unless you also use
-fdiagnostics-show-option.
Both of these options are default in newer gcc (such as 4.8.1);
but incl
+1
This begs the question as to why they're options in the first place?
I.E. there must be a downside requiring an option to allow to disable,
or is this a case of redundant options?
cheers,
Pádraig.
[adding cygwin]
On 04/29/2013 04:23 PM, Paul Eggert wrote:
> ---
> +
> + tests: don't assume getdtablesize () <= 1000
> + * modules/cloexec-tests:
> + * modules/dup2-tests:
> + * modules/dup3-tests:
> + * modules/nonblocking-tests:
> + * modules/posix_spawn_file_action
