From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb@sourceware.org>,
"'Eli Zaretskii'" <eliz@gnu.org>
Cc: <tromey@redhat.com>, <dave.korn.cygwin@googlemail.com>,
<msnyder@vmware.com>
Subject: RE: A strange gcc behavior, and an argument against -Wno-unused
Date: Tue, 13 Oct 2009 15:33:00 -0000 [thread overview]
Message-ID: <05bc01ca4c1a$7110fd80$5332f880$@u-strasbg.fr> (raw)
In-Reply-To: <200910131509.40897.pedro@codesourcery.com>
> -----Message d'origine-----
> De : gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] De la
> part de Pedro Alves
> Envoyé : Tuesday, October 13, 2009 4:10 PM
> À : gdb@sourceware.org; Eli Zaretskii
> Cc : tromey@redhat.com; dave.korn.cygwin@googlemail.com;
> msnyder@vmware.com
> Objet : Re: A strange gcc behavior, and an argument against -Wno-unused
>
> Since Michael has committed his patch meanwhile, in the
> interest of moving a bit forward, how 'bout we give this a
> try, then? No new warnings caught on an
> 'x86_64-linux --enable-targets=all' at -O2 build.
Isn't this going to make troubles if
a standard function is defined as a pascal procedure
i. e. with return type (void) in most implementation
but returning something else on some "exotic" system?
I thought there were some examples
but can't remember any exact ones :(
Maybe related to signals?
Pierre Muller
Pascal language support maintainer for GDB
next prev parent reply other threads:[~2009-10-13 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 0:48 Michael Snyder
2009-10-10 2:24 ` Dave Korn
2009-10-10 16:45 ` Pedro Alves
2009-10-10 18:08 ` Eli Zaretskii
2009-10-10 18:24 ` Pedro Alves
2009-10-10 18:25 ` Tom Tromey
2009-10-10 18:37 ` Eli Zaretskii
2009-10-10 18:50 ` Pedro Alves
2009-10-10 19:46 ` Eli Zaretskii
2009-10-13 14:09 ` Pedro Alves
2009-10-13 15:33 ` Pierre Muller [this message]
2009-10-13 16:42 ` Tom Tromey
2009-10-13 15:48 ` Tom Tromey
2009-10-14 19:45 ` Pedro Alves
2009-10-10 18:30 ` Tom Tromey
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='05bc01ca4c1a$7110fd80$5332f880$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=dave.korn.cygwin@googlemail.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.com \
/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