[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-10 Thread danglin at gcc dot gnu dot org
--- Comment #13 from danglin at gcc dot gnu dot org 2007-02-10 19:51 --- Subject: Bug 30634 Author: danglin Date: Sat Feb 10 19:51:40 2007 New Revision: 121802 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121802 Log: PR target/30634 * pa.md (movdf): For 64-bit

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-10 Thread danglin at gcc dot gnu dot org
--- Comment #14 from danglin at gcc dot gnu dot org 2007-02-10 19:54 --- Subject: Bug 30634 Author: danglin Date: Sat Feb 10 19:54:33 2007 New Revision: 121803 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121803 Log: PR target/30634 * pa.md (movdf): For 64-bit

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-10 Thread danglin at gcc dot gnu dot org
--- Comment #15 from danglin at gcc dot gnu dot org 2007-02-10 20:24 --- Fixed by patch on 4.2 and trunk. -- danglin at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-04 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Comment #8 from dave at hiauly1 dot hia dot nrc dot ca 2007-02-04 17:06 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 My patch just exposed a latent bug. Does this fail on the trunk also the same way? If not can you trace to see where the

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-04 Thread pinskia at gcc dot gnu dot org
--- Comment #9 from pinskia at gcc dot gnu dot org 2007-02-04 17:13 --- Can you try the following C code? double f(void) { long long t = -1; double t1; __builtin_memcpy(t1, t, sizeof(long long)); return t; } If the above is broken also, then my patch just exposed the above

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-04 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Comment #10 from dave at hiauly1 dot hia dot nrc dot ca 2007-02-04 17:37 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 Can you try the following C code? double f(void) { long long t = -1; double t1; __builtin_memcpy(t1, t,

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-04 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Comment #11 from dave at hiauly1 dot hia dot nrc dot ca 2007-02-04 19:55 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 Can you try the following C code? double f(void) { long long t = -1; double t1; __builtin_memcpy(t1, t,

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-04 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Comment #12 from dave at hiauly1 dot hia dot nrc dot ca 2007-02-04 23:31 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 Also I don't see anything wrong with the expand's RTL. The difference between 4.1.1 and 4.2's RTL is that we don't go

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-03 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Comment #5 from dave at hiauly1 dot hia dot nrc dot ca 2007-02-04 01:07 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 --- Comment #3 from kargl at gcc dot gnu dot org 2007-01-30 02:53 --- A scan of libgfortran/ChangeLog and

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-03 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-02-04 01:41 --- The failure was introduced in revision 121076: My patch just exposed a latent bug. Does this fail on the trunk also the same way? If not can you trace to see where the difference in the IR between the 4.2 branch

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-02-03 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Comment #7 from dave at hiauly1 dot hia dot nrc dot ca 2007-02-04 01:55 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 My patch just exposed a latent bug. Does this fail on the trunk also the same way? If not can you trace to see where the

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-01-30 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca 2007-01-30 14:51 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 --- Comment #3 from kargl at gcc dot gnu dot org 2007-01-30 02:53 --- A scan of libgfortran/ChangeLog and

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-01-29 Thread danglin at gcc dot gnu dot org
--- Comment #1 from danglin at gcc dot gnu dot org 2007-01-30 01:16 --- Maybe I'll finally get the details right: Target: hppa64-hp-hpux11.00 Configured with: ../gcc/configure --with-gnu-as --with-as=/opt/gnu64/bin/as --with-ld=/usr/ccs/bin/ld --enable-shared

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-01-29 Thread danglin at gcc dot gnu dot org
--- Comment #2 from danglin at gcc dot gnu dot org 2007-01-30 01:20 --- Test didn't fail at revision 121050. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30634

[Bug target/30634] FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

2007-01-29 Thread kargl at gcc dot gnu dot org
--- Comment #3 from kargl at gcc dot gnu dot org 2007-01-30 02:53 --- A scan of libgfortran/ChangeLog and gcc/fortran/ChangeLog does not reveal anything that would cause this failure. Can you identify the exact commit that causes the problem? Perhaps, something got mismerged from