--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.1.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31150
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31150
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-04-16 00:56 ---
This was introduced by the fix for PR 21478.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from eres at il dot ibm dot com 2007-06-25 12:31 ---
I would like to be assigned to this bug.
Thanks,
Revital
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31150
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |eres at il dot ibm dot com
|dot org
--- Comment #3 from eres at il dot ibm dot com 2007-06-26 07:42 ---
Created an attachment (id=13791)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13791&action=view)
fix PR31150
Attached is a patch to initialize the scalar elmenets of the array
which should fix this problem.
cha
--- Comment #4 from patchapp at dberlin dot org 2007-06-28 05:50 ---
Subject: Bug number PR31150
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2007-06/msg02037.html
--
http://gcc.gnu.org/bugzilla/sh
--- Comment #5 from eres at il dot ibm dot com 2007-06-28 11:55 ---
(Form off-line discussion with Richard Guenther)
For-
char str[2][16] = {"thisis16charslo","thisis16charslo"};
On ppc64 we will get -
static char C.0[2][16] = {"thisis16charslo", "thisis16charslo"};
while on x86_64
--- Comment #6 from jakub at gcc dot gnu dot org 2007-08-23 20:36 ---
It is unfortunate that gimple can only initialize the whole array, unless
__builtin_memcpy is used. Unfortunately __builtin_memcpy has a different
drawback - the var will be forced to be TREE_ADDRESSABLE even when it