This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/59934] Bootstrap fail since r206941: expmed.h:252:33: error: array subscript is above array bounds
- From: "law at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 24 Jan 2014 22:53:58 +0000
- Subject: [Bug bootstrap/59934] Bootstrap fail since r206941: expmed.h:252:33: error: array subscript is above array bounds
- Auto-submitted: auto-generated
- References: <bug-59934-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59934
--- Comment #9 from Jeffrey A. Law <law at redhat dot com> ---
Jakub,
I think your second approach is the better solution. It'll abort rather than
silently returning a value which may or may not be appropriate in the caller's
context.
ie, returning 0 when we don't (for example) have partial modes may avoid this
particular problem, but may cause issues elsewhere.
Granted this code only has one user, but I'd rather play things like this
defensively and just abort if we get into a situation that's not supposed to
happen.
I'll start an s390x build and see where the 2nd approach takes us...