From: Richard Zidlicky <rz@linux-m68k.org>
To: Bernardo Innocenti <bernie@develer.com>
Cc: Andreas Schwab <schwab@suse.de>,
Roman Zippel <zippel@linux-m68k.org>,
peter@baradas.org, Matthias Klose <doko@cs.tu-berlin.de>,
gcc@gcc.gnu.org, Gunther Nikl <gni@gecko.de>
Subject: Re: more m68k breakage on m68k-linux
Date: Thu, 04 Mar 2004 18:45:00 -0000 [thread overview]
Message-ID: <20040304184301.GA1647@linux-m68k.org> (raw)
In-Reply-To: <40465E6E.5070301@develer.com>
On Wed, Mar 03, 2004 at 11:38:38PM +0100, Bernardo Innocenti wrote:
> To make sure this particular case will never show up again
> on any backend, I'd like to add some static sanity checks.
> We can't use the preprocessor because it doesn't know about
> structure sizes.
actually, in this particular case the compiler has all
necessary information to catch the error, any chance
gcc could grasp simple memcpy overruns when the size
of both operands is known?
Adding yet another check for an extremely unlikely condition
may not be a good tradeoff at this place.
Richard
next prev parent reply other threads:[~2004-03-04 18:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 1:50 Bernardo Innocenti
2004-01-18 4:52 ` Bernardo Innocenti
2004-01-18 9:59 ` Matthias Klose
2004-01-18 10:07 ` Bernardo Innocenti
2004-01-20 9:15 ` Andreas Schwab
2004-01-20 10:36 ` Bernardo Innocenti
2004-03-01 20:15 ` Richard Zidlicky
2004-03-01 22:05 ` Richard Zidlicky
2004-03-02 0:18 ` Bernardo Innocenti
2004-03-02 9:14 ` Richard Zidlicky
2004-03-02 10:42 ` Gunther Nikl
2004-03-02 18:19 ` Richard Henderson
2004-03-02 19:33 ` Roman Zippel
2004-03-02 21:32 ` Richard Henderson
2004-03-02 22:26 ` Richard Zidlicky
2004-03-03 8:53 ` Bernardo Innocenti
2004-03-03 10:13 ` Roman Zippel
2004-03-03 11:03 ` Andreas Schwab
2004-03-03 22:38 ` Bernardo Innocenti
2004-03-04 0:35 ` Richard Henderson
2004-03-04 7:25 ` Gunther Nikl
2004-03-04 18:45 ` Richard Zidlicky [this message]
2004-03-04 22:46 ` Andreas Schwab
2004-03-04 10:58 ` Gunther Nikl
2004-03-04 13:27 ` Bernardo Innocenti
2004-03-04 13:45 ` Roman Zippel
2004-03-04 15:32 ` Gunther Nikl
2004-03-07 15:05 ` Bernardo Innocenti
2004-03-08 16:31 ` Gunther Nikl
2004-03-08 21:38 ` Bernardo Innocenti
2004-03-09 8:40 ` Gunther Nikl
2004-03-09 22:35 ` Bernardo Innocenti
[not found] ` <20040308181401.0DB3498C8A@baradas.org>
2004-03-08 21:45 ` You ucLinux patches break RTEMS building Bernardo Innocenti
2004-03-03 8:22 ` more m68k breakage on m68k-linux Bernardo Innocenti
2004-03-03 13:27 ` Richard Zidlicky
2004-03-01 22:30 ` Andreas Schwab
2004-03-02 0:07 ` Bernardo Innocenti
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=20040304184301.GA1647@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=bernie@develer.com \
--cc=doko@cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=gni@gecko.de \
--cc=peter@baradas.org \
--cc=schwab@suse.de \
--cc=zippel@linux-m68k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).