From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sources.redhat.com
Subject: Re: Fix aliasing violations
Date: Sat, 23 Oct 2004 19:08:00 -0000 [thread overview]
Message-ID: <je3c05fe3n.fsf@sykes.suse.de> (raw)
In-Reply-To: <20041023183729.GA4783@nevyn.them.org> (Daniel Jacobowitz's message of "Sat, 23 Oct 2004 14:37:29 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> On Sat, Oct 23, 2004 at 08:26:28PM +0200, Andreas Schwab wrote:
>> The macro GROW_VECT in ada-lang.h violates the C aliasing rules.
>>
>> Andreas.
>>
>> 2004-10-23 Andreas Schwab <schwab@suse.de>
>>
>> * ada-lang.c (grow_vect): Return the new array instead of
>> expecting pointer to pointer to avoid violation of aliasing rules.
>> * ada-lang.h (GROW_VECT): Adapt call to grow_vect.
>
> I assume newer versions of GCC warn about this?
Yes, that's -Wstrict-aliasing, part of -Wall.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-10-23 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 18:28 Andreas Schwab
2004-10-23 18:37 ` Daniel Jacobowitz
2004-10-23 19:08 ` Andreas Schwab [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=je3c05fe3n.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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