From: Eli Zaretskii <eliz@gnu.org>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Avoid invalid parameter warnings in C runtime function for mingw builtr GDB
Date: Tue, 13 Aug 2013 16:35:00 -0000 [thread overview]
Message-ID: <838v05pn04.fsf@gnu.org> (raw)
In-Reply-To: <"001401ce9805$6cce7050$466b50f0$@muller"@ics-cnrs.unistra.fr>
> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Cc: <gdb-patches@sourceware.org>
> Date: Tue, 13 Aug 2013 11:13:49 +0200
>
> Would that be correct?
>
> #if O_CLOEXEC
> static int fopen_e_ever_failed = 0;
> #else
> static int fopen_e_ever_failed = 1;
> #endif
Yes, but Tom's suggestion is more elegant.
next prev parent reply other threads:[~2013-08-13 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"002201ce9414$7e0d7130$7a285390$@muller"@ics-cnrs.unistra.fr>
2013-08-09 14:09 ` Eli Zaretskii
2013-08-13 9:13 ` Pierre Muller
[not found] ` <41630.7793967009$1376385245@news.gmane.org>
2013-08-13 15:37 ` Tom Tromey
2013-08-14 11:38 ` [RFA-v2] Avoid invalid parameter warnings in C runtime function for mingw built GDB Pierre Muller
[not found] ` <520b6c37.e9e6440a.7cfb.45fcSMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-14 12:01 ` Pedro Alves
2013-08-14 12:12 ` [RFA-v3] " Pierre Muller
2013-09-13 22:35 ` Pierre Muller
[not found] ` <5233934f.8360440a.1d3e.ffffa937SMTPIN_ADDED_BROKEN@mx.google.com>
2013-09-13 23:08 ` Doug Evans
2013-09-14 6:30 ` Pierre Muller
[not found] ` <"001401ce9805$6cce7050$466b50f0$@muller"@ics-cnrs.unistra.fr>
2013-08-13 16:35 ` Eli Zaretskii [this message]
[not found] <22647.6293908947$1375951926@news.gmane.org>
2013-08-09 15:26 ` [RFC] Avoid invalid parameter warnings in C runtime function for mingw builtr GDB Tom Tromey
2013-08-08 8:51 Pierre Muller
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=838v05pn04.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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