public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xarthisius.kk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53900] [regression] Too optimistic on a alignment assert
Date: Fri, 28 Dec 2012 17:47:00 -0000 [thread overview]
Message-ID: <bug-53900-4-RsBjgCLczj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53900-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53900
Kacper Kowalik <xarthisius.kk at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xarthisius.kk at gmail dot
| |com
--- Comment #5 from Kacper Kowalik <xarthisius.kk at gmail dot com> 2012-12-28 17:47:12 UTC ---
(In reply to comment #1)
> You tell the compiler array is aligned, so what do you expect?
This regression was introduced by:
http://gcc.gnu.org/viewcvs?view=revision&revision=172424
2011-04-14 Richard Guenther <rguenther@suse.de>
* tree.h (get_object_alignment_1): Declare.
* builtins.c (get_object_alignment_1): Split out worker from ...
(get_object_alignment): ... here.
* fold-const.c (get_pointer_modulus_and_residue): Use
get_object_alignment_1.
* gcc.dg/fold-bitand-4.c: Move ...
* c-c++-common/fold-bitand-4.c: ... here. Adjust slightly.
Could you please verify that it's intended behaviour and/or indicate if
provided testcase is a valid/invalid code?
Thank you in advance,
Kacper Kowalik
next prev parent reply other threads:[~2012-12-28 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 14:57 [Bug c++/53900] New: " gael.guennebaud at gmail dot com
2012-07-09 15:23 ` [Bug c++/53900] [regression] " rguenth at gcc dot gnu.org
2012-07-09 16:12 ` gael.guennebaud at gmail dot com
2012-07-09 16:19 ` rguenth at gcc dot gnu.org
2012-07-10 11:09 ` gael.guennebaud at gmail dot com
2012-12-28 17:47 ` xarthisius.kk at gmail dot com [this message]
2013-01-07 4:27 ` pinskia at gcc dot gnu.org
2013-01-07 10:19 ` chtz at informatik dot uni-bremen.de
2013-01-07 10:22 ` pinskia at gcc dot gnu.org
2015-02-19 15:27 ` jacob.benoit.1 at gmail dot com
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=bug-53900-4-RsBjgCLczj@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).