From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] ``struct value'' cleanups
Date: Sat, 16 Mar 2002 17:28:00 -0000 [thread overview]
Message-ID: <3C93F155.8030007@cygnus.com> (raw)
In-Reply-To: <20020316201740.A10905@nevyn.them.org>
> On Sat, Mar 16, 2002 at 08:04:18PM -0500, Andrew Cagney wrote:
>
>> @@ -166,9 +158,10 @@
>> union
>> {
>> long contents[1];
>> - double force_double_align;
>> - LONGEST force_longlong_align;
>> - char *literal_data;
>> + DOUBLEST force_doublest_align;
>> + LONGEST force_longest_align;
>> + CORE_ADDR force_core_addr_align;
>> + void *force_pointer_aligh;
>> }
>> aligner;
>> /* Do not add any new members here -- contents above will trash them */
>
>
> (I suppose literal_data was not actually used anywhere either? It
> seems different than the other members...)
Rebuilt after the change and a grep didn't show anything.
> Typo, force_pointer_aligh.
I'm tempted to leave it in just to see if it also manages to remain
there for 8 years :-) (thanks)
Andrew
prev parent reply other threads:[~2002-03-17 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 17:04 Andrew Cagney
2002-03-16 17:17 ` Daniel Jacobowitz
2002-03-16 17:28 ` Andrew Cagney [this message]
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=3C93F155.8030007@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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