Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] display vector types using vector_size syntax
Date: Tue, 11 Sep 2012 22:07:00 -0000	[thread overview]
Message-ID: <504FB607.1000507@earthlink.net> (raw)
In-Reply-To: <504EFFE4.1090007@broadcom.com>

On 9/11/12 2:09 AM, Andrew Burgess wrote:
> On 10/09/2012 11:06 PM, Joel Brobecker wrote:
>>> Andrew> I'd like to change the behaviour to this:
>>> Andrew> (gdb) ptype vector
>>> Andrew> type = char ((vector_size(4)))
>>> Andrew> (gdb) whatis vector
>>> Andrew> type = char ((vector_size(4)))
>>>
>>> Seems reasonable to me.
>>
>> Just a thought: How about
>>
>>      type = char __attribute__ ((vector_size(4)))
>>
>> ?
>>
>> It know it's a lot more verbose, but the later speaks a lot more
>> to me than the original proposal...
>
> I only dropped this to avoid clutter, but I don't really mind either way.
>
> I'll give it a couple more days for people to reply, then commit a 
> version with "__attibute__".

I vote for __attribute__ too.  Although more cluttered, it immediately 
says "GCC extensions are hanging about" while the vector_size by itself 
looks like it could be one of the app's symbols that somehow found its 
way into the type (and users will no doubt assume that it's a GDB bug :-) ).

Stan
stan@codesourcery.com


  parent reply	other threads:[~2012-09-11 22:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03 10:56 Andrew Burgess
2012-09-10 17:12 ` Tom Tromey
2012-09-10 22:06   ` Joel Brobecker
2012-09-11  9:11     ` Andrew Burgess
2012-09-11 11:35       ` Pedro Alves
2012-09-11 22:07       ` Stan Shebs [this message]
2012-09-14 21:27   ` Andrew Burgess
2012-10-26 18:53     ` Tom Tromey
2012-10-29 10:54       ` Andrew Burgess
2012-10-30 20:46         ` 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=504FB607.1000507@earthlink.net \
    --to=stanshebs@earthlink.net \
    --cc=gdb-patches@sourceware.org \
    /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