Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Peter O'Gorman" <gdb-patches@mlists.thewrittenword.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: minor portability patches
Date: Tue, 21 Sep 2010 21:09:00 -0000	[thread overview]
Message-ID: <20100921195449.GE32745@tw.local> (raw)
In-Reply-To: <m3lj6veyzv.fsf@fleche.redhat.com>

On Tue, Sep 21, 2010 at 12:24:20PM -0600, Tom Tromey wrote:
> Me neither.  I'm not sure how we handle static linking against python,
> or whether we even support it.
> 
> Peter> __FUNCTION__ is a gccism.
> 
> BFD patches should go to the binutils list.
> 

I should have know that, sorry.

> Peter> At least solaris cc complained about returning from void functions.
> 
> This one and the cplus_struct_default patch are obvious once you have a
> ChangeLog entry.

For those then (0004-* and 0006-* in my earlier mail):

2010-09-21  Peter O'Gorman  <pogma@thewrittenword.com>

	* dwarf2loc.c (dwarf_expr_dwarf_call, needs_frame_dwarf_call): Do
	not return from void functions.
	* gdbtypes.c (cplus_struct_default): Initialize portably.

0002-*

	* aix-thread.c: Build fixes for aix6.1.

0003-*:

	* configure.ac: Do not add -rdynamic for non GCC compilers.

Thanks,
Peter
-- 
Peter O'Gorman
pogma@thewrittenword.com


  parent reply	other threads:[~2010-09-21 19:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 19:59 Peter O'Gorman
2010-09-21 20:06 ` Tom Tromey
2010-09-21 20:40   ` Joel Brobecker
2010-09-21 20:50     ` Peter O'Gorman
2010-09-21 21:56       ` Joel Brobecker
2010-09-21 21:09   ` Peter O'Gorman [this message]
2010-09-22 16:15   ` Doug Evans
2010-09-23 22:03 ` Jan Kratochvil

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=20100921195449.GE32745@tw.local \
    --to=gdb-patches@mlists.thewrittenword.com \
    --cc=gdb-patches@sourceware.org \
    --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