From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Neo Jia <neojia@gmail.com>, gdb ml <gdb@sourceware.org>
Subject: Re: gdb plugin status?
Date: Wed, 06 Aug 2008 20:46:00 -0000 [thread overview]
Message-ID: <1218055425.6617.5.camel@localhost.localdomain> (raw)
In-Reply-To: <m3d4klkhi2.fsf@fleche.redhat.com>
On Wed, 2008-08-06 at 14:36 -0600, Tom Tromey wrote:
> >>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
>
> Tom> FWIW, my build uses -fno-strict-aliasing, which disables this warning.
>
> Thiago> Anyway, the PYTHON_CFLAGS are only used to compile files under the
> Thiago> python/ subdir. I just checked here and varobj.c isn't compiled with it.
>
> I suppose we should widen this to any file that includes python-internal.h.
>
> Or, rework things so that varobj.c does not have to include that file.
> Given that these flags that are needed by python headers are basically
> bug workarounds, it might be nice to try to limit the fallout.
Right, nothing outside python/ is supposed to include python-internal.h
(that's why I put the -internal suffix :-) ). varobj.c does it at the
moment because we didn't get around to cleanup the MI python patch yet.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2008-08-06 20:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 17:11 Neo Jia
2008-08-03 17:31 ` Daniel Jacobowitz
2008-08-03 17:43 ` Neo Jia
2008-08-03 21:53 ` Thiago Jung Bauermann
2008-08-03 21:56 ` Thiago Jung Bauermann
[not found] ` <5d649bdb0808040042o34b759edxe6c11e16588214f6@mail.gmail.com>
2008-08-04 14:28 ` Thiago Jung Bauermann
2008-08-05 7:33 ` Neo Jia
2008-08-05 13:47 ` Thiago Jung Bauermann
[not found] ` <5d649bdb0808051553g6ee22cbfr80cfa43cd56e870c@mail.gmail.com>
2008-08-06 3:27 ` Thiago Jung Bauermann
2008-08-06 4:40 ` Tom Tromey
2008-08-06 5:44 ` Thiago Jung Bauermann
2008-08-06 20:37 ` Tom Tromey
2008-08-06 20:46 ` Thiago Jung Bauermann [this message]
2008-08-07 7:11 ` Neo Jia
2008-08-07 18:37 ` Tom Tromey
2008-08-07 19:06 ` Thiago Jung Bauermann
2008-08-12 15:25 ` Thiago Jung Bauermann
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=1218055425.6617.5.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=neojia@gmail.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