--- Additional Comments From kkojima at gcc dot gnu dot org 2005-03-09
23:58 ---
I'm taking a look at the uses of MEM_READONLY_P, though I'm not
sure which one has the similar issue. It looks that modified_in_p
has the same problem with modified_between_p.
BTW, it's better to change
--- Additional Comments From amylaar at gcc dot gnu dot org 2005-03-08
21:58 ---
(In reply to comment #1)
I've traced what's going on:
http://gcc.gnu.org/ml/gcc-patches/2005-03/msg00525.html
It includes a patch for comment.
The sh64 port is partcularily exposed in
--- Additional Comments From kkojima at gcc dot gnu dot org 2005-03-07
00:20 ---
I've traced what's going on:
http://gcc.gnu.org/ml/gcc-patches/2005-03/msg00525.html
It includes a patch for comment.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20331
--
What|Removed |Added
Summary|[3.4/4.0/41 Regression] |[3.4/4.0/4.1 Regression]
|Wrong code generation for |Wrong code generation for
--
What|Removed |Added
Target Milestone|--- |4.1.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20331
