Re: Debugger support for __float128 type?

2015-09-30 Thread Mark Kettenis
> Date: Wed, 30 Sep 2015 19:33:44 +0200 (CEST) > From: "Ulrich Weigand" > > Hello, > > I've been looking into supporting __float128 in the debugger, since we're > now introducing this type on PowerPC. Initially, I simply wanted to do > whatever GDB does on Intel, but it turns out debugging __fl

gcc-4.9-20150930 is now available

2015-09-30 Thread gccadmin
Snapshot gcc-4.9-20150930 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20150930/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.9 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Re: Debugger support for __float128 type?

2015-09-30 Thread Joseph Myers
On Wed, 30 Sep 2015, Ulrich Weigand wrote: > - Extend the official DWARF standard in some way I think you should do this. Note that TS 18661-4 will be coming out very soon, and includes (optional) types * _FloatN, where N is 16, 32, 64 or >= 128 and a multiple of 32; * _DecimalN, where N >= 3

Debugger support for __float128 type?

2015-09-30 Thread Ulrich Weigand
Hello, I've been looking into supporting __float128 in the debugger, since we're now introducing this type on PowerPC. Initially, I simply wanted to do whatever GDB does on Intel, but it turns out debugging __float128 doesn't work on Intel either ... The most obvious question is, how should the

Re: how well does gcc support type-specific pointer formats?

2015-09-30 Thread Mikael Pettersson
Richard Biener writes: > On Wed, Sep 30, 2015 at 11:23 AM, Mikael Pettersson > wrote: > > Does gcc allow backends to have a say in how pointers are represented > > (bits beyond the address), what happens in conversions between pointer > > types, and what happens in conversions between pointer

Re: how well does gcc support type-specific pointer formats?

2015-09-30 Thread Richard Biener
On Wed, Sep 30, 2015 at 11:23 AM, Mikael Pettersson wrote: > Does gcc allow backends to have a say in how pointers are represented > (bits beyond the address), what happens in conversions between pointer > types, and what happens in conversions between pointers and uintptr_t? > > The target in que

how well does gcc support type-specific pointer formats?

2015-09-30 Thread Mikael Pettersson
Does gcc allow backends to have a say in how pointers are represented (bits beyond the address), what happens in conversions between pointer types, and what happens in conversions between pointers and uintptr_t? The target in question has: - one pointer format and set of load/store instructions fo