A trimmed down version of the code which produce the ice is below; The full
code once compile with version 4.1.0, I believe
>>
!
SUBROUTINE POSL(LAT,LON,JUL,HEURE,MIN,PAZ)
IMPLICIT NONE
!
REAL,SAVE :: XPI! Pi
REAL, DIMENSION(:), INTENT(IN):: LAT, LON, JUL, HEURE
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||ice-on-valid-code
Summary|ICE in gfc_dep_resolver |[4.
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-14 03:10 ---
Confirmed, reduced testcase:
IMPLICIT NONE
REAL, DIMENSION(2) :: ZXLON
WHERE(ZXLON < 0.0)
ZXLON(:) = 1
END WHERE
END PROGRAM
--
pinskia at gcc dot gnu dot org changed:
--- Comment #2 from kargl at gcc dot gnu dot org 2006-12-14 03:28 ---
(In reply to comment #1)
> Confirmed, reduced testcase:
> IMPLICIT NONE
> REAL, DIMENSION(2) :: ZXLON
> WHERE(ZXLON < 0.0)
> ZXLON(:) = 1
> END WHERE
> END PROGRAM
>
A work
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||ice-on-valid-code
Target Milestone|--- |4.1
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-12-14 03:59 ---
(In reply to comment #2)
> but only if we don't honor NaNs or signed zeros.
Some of these optimizations can be done even without worrying about NaNs
because of -fcx-limited-range .
--
http://gcc.gnu.org/bugzill
On such platforms:
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
gcc version 3.3.3 (SuSE Linux)
Source Code:
void func(unsigned char *buf)
{
unsigned short *p, a, b, c, d;
unsigned int *q, m, n;
unsigned int i1 = 0x;
unsigned int i2 = 0x;
unsign
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-14 04:53 ---
You are violating C aliasing rules.
C aliasing rules say you can only access a variable (or an array) by the
orginal type (signed or unsigned version) or a character type (or qualified
types of those).
You have an a
--- Comment #109 from pinskia at gcc dot gnu dot org 2006-12-14 04:53
---
*** Bug 30208 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from kargl at gcc dot gnu dot org 2006-12-14 05:03 ---
I have a patch/hack to fix this.
--
kargl at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-14 05:19 ---
Actually there are three seperate issues:
1) for my recent vector patch, it was a c-gimplifier issue with respect of not
setting GIMPLE_REG_P on the decls for the compount literals, this helps with
complex typed vari
Testcase:
_Complex float f(float x, float y)
{
_Complex float a = (_Complex float){x};
return a;
}
--
Summary: C++ front-end rejects valid compound literal (with
complex types)
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
--- Comment #9 from ian at gcc dot gnu dot org 2006-12-14 05:49 ---
Subject: Bug 19756
Author: ian
Date: Thu Dec 14 05:49:06 2006
New Revision: 119855
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119855
Log:
PR c++/19564
PR c++/19756
gcc/:
* c-typeck.c
--- Comment #8 from ian at gcc dot gnu dot org 2006-12-14 05:49 ---
Subject: Bug 19564
Author: ian
Date: Thu Dec 14 05:49:06 2006
New Revision: 119855
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119855
Log:
PR c++/19564
PR c++/19756
gcc/:
* c-typeck.c
--- Comment #9 from ian at airs dot com 2006-12-14 06:03 ---
Will be fixed in gcc 4.3.
--
ian at airs dot com changed:
What|Removed |Added
Status|NEW
--- Comment #10 from ian at airs dot com 2006-12-14 06:04 ---
Will be fixed in gcc 4.3.
--
ian at airs dot com changed:
What|Removed |Added
CC|
--- Comment #7 from jv244 at cam dot ac dot uk 2006-12-14 06:41 ---
(In reply to comment #6)
> More information. I get Tobias bad result with -m64 on x86-64-Linux. The
> problem goes away with -m32.
>
> $ gfortran -m32 pr30200-2.f90
> $ ./a.out
> Axyz
> $ gfortran -m64 pr30200-2.f90
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Summary|regressions in the gfortran |[4.3 Regression] regressions
|testsuite with -ftree
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-12-14 06:50 ---
Fixed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRM
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-12-14 06:51 ---
Fixed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIGNED
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-12-14 06:53 ---
The spu-elf part of this bug is not a regression, the reason why we have CDI
here is because spu-elf supports subregs of TI mode for CDI so we get that
mode. Note the dataflow branch gets rid of this bug.
--
pin
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-12-14 07:05 ---
(In reply to comment #5)
> one of the vectorizer testcases (vect-reduc-dot-u8b.c) still fails with
> modify.diff.txt on MODIFY_EXPR where the right hand side is a call to a
> builtin function (rs6000_builtin_mul_wid
--- Comment #31 from choe dot hwanjin at gmail dot com 2006-12-14 07:29
---
Created an attachment (id=12801)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12801&action=view)
basic_string test code with visibility option
Something similar happens when I use GCC option -fvisibility
--- Comment #32 from choe dot hwanjin at gmail dot com 2006-12-14 07:30
---
(From update of attachment 12801)
Something similar happens when I use GCC option -fvisibility=hidden.
I made a DSO which uses basic_string<>.
And the main function created a basic_string instance with default
101 - 124 of 124 matches
Mail list logo
