--- Comment #3 from burnus at gcc dot gnu dot org 2008-05-27 16:34 ---
gfortran should do better. NAG f95 detects at compile time:
dzeta=matmul(U,B)
Error: Array shapes differ in dimension 1 (extent 6 and 7)
Here, dzeta is (6,12) and matmul(U,B) is (7,12).
gfortran does not even de
--- Comment #7 from burnus at gcc dot gnu dot org 2008-05-27 19:22 ---
Found it - took only 4 hours.
FIXED on the trunk (4.4.0). Thanks for reporting the bug.
--
burnus at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #8 from burnus at gcc dot gnu dot org 2008-05-27 19:22 ---
Subject: Bug 36316
Author: burnus
Date: Tue May 27 19:22:01 2008
New Revision: 136052
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136052
Log:
2008-05-27 Tobias Burnus <[EMAIL PROTECTED]>
PR fort
--- Comment #6 from kih at mail dot nerc-essc dot ac dot uk 2008-05-27
19:57 ---
Subject: RE: gfortran and cc1 error
The distribution came from:
http://r.research.att.com/tools/
so I guess I should take it up with them.
Regards
Kevin
-Original Message-
From: fxcoudert at
--- Comment #3 from hjl at gcc dot gnu dot org 2008-05-27 20:19 ---
Subject: Bug 35767
Author: hjl
Date: Tue May 27 20:18:33 2008
New Revision: 136054
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136054
Log:
gcc/
2008-05-27 H.J. Lu <[EMAIL PROTECTED]>
PR target/357
--- Comment #5 from hjl at gcc dot gnu dot org 2008-05-27 20:19 ---
Subject: Bug 35771
Author: hjl
Date: Tue May 27 20:18:33 2008
New Revision: 136054
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136054
Log:
gcc/
2008-05-27 H.J. Lu <[EMAIL PROTECTED]>
PR target/357
--- Comment #6 from hjl dot tools at gmail dot com 2008-05-27 20:22 ---
Fixed.
--
hjl dot tools at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRM
--- Comment #4 from hjl dot tools at gmail dot com 2008-05-27 20:22 ---
Fixed.
--
hjl dot tools at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRM
--- Comment #7 from mikpe at it dot uu dot se 2008-05-27 20:48 ---
(In reply to comment #6)
> Fixed.
>
I added the fix to the latest gcc-4.3 snapshot and bootstrapped it.
I then tested both the original application that failed (Erlang)
as well as the latest Linux kernel. Both built and
ran,ada,obj-c++,java
Thread model: posix
gcc version 4.4.0 20080527 (experimental) [trunk revision 136058] (GCC)
--
Summary: f951 link failure on i686-apple-darwin9
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
--- Comment #3 from hutchinsonandy at gcc dot gnu dot org 2008-05-28 00:44
---
Committed.
Will do 4.3 latter.
2008-05-12 Andy Hutchinson <[EMAIL PROTECTED]>
* config/avr/avr.h (MAX_OFILE_ALIGNMENT): Define.
--
hutchinsonandy at gcc dot gnu dot org changed:
What|Re
--
hutchinsonandy at gcc dot gnu dot org changed:
What|Removed |Added
Status|NEW |SUSPENDED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32871
+++ This bug was initially created as a clone of Bug #35619 +++
That one was closed with no resolution, and I still can't build gcc-3.4.0.
Help!!!)
Attempting to build gcc-4.3.0 on Suse 10.1 with gcc compiler
Exact version of gcc used to build gcc-4.3.0:
gcc version 4.2.1
Options when GCC was
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-05-28 01:11 ---
I have built GCC with -mcpu=cell recently and it worked.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #16 from pinskia at gcc dot gnu dot org 2008-05-28 01:13
---
(In reply to comment #15)
> Closed as invalid.
This bug is not invalid, just you are not building GCC the recommended way.
--
pinskia at gcc dot gnu dot org changed:
What|Removed
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35619
--- Comment #17 from pinskia at gcc dot gnu dot org 2008-05-28 01:15
---
*** Bug 36349 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-05-28 01:15 ---
This is a dup of bug 35619.
Workaround: don't build in the source directory.
Moral of the story, follow recommended instructions of building.
*** This bug has been marked as a duplicate of 35619 ***
--
pinskia
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfi
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-05-28 01:19 ---
This is being worked on already. Daniel Franke is working on it.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #4 from terry at chem dot gu dot se 2008-05-28 02:00 ---
Somewhat reduced testcase that exhibits the same behaviour:
program distgeom
implicit none
real(kind=8),dimension(7,12)::B
real(kind=8),dimension(7,7)::U
real(kind=8),dimension(6,12)::dzeta
call random_number(U)
call r
--- Comment #2 from phorgan1 at gmail dot com 2008-05-28 03:59 ---
Build in objdir fails similarly when building libiberty.a Still has the same
multiple definitions.
make[3]: Entering directory
`/usr/local/gcc-4.3.0/objdir/build-x86_64-unknown-linux-gnu/fixincludes'
gcc -c -g -O2 -W -W
--- Comment #3 from pinskia at gcc dot gnu dot org 2008-05-28 04:24 ---
Can you make sure that your source tree is clean before building in the object
directory?
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #4 from phorgan1 at gmail dot com 2008-05-28 04:44 ---
I reinstalled gcc-4.3.0 from the tar.gz file, and extracted it in
/usr/local/gcc-4.3.0. Then I made a completely separate object directory
/usr/local/gcc-4.3.0-objdir. From within that directory I executed
../gcc-4.3.0/
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-05-28 04:46 ---
>gcc -g -O2 -o fixincl fixincl.o fixtests.o fixfixes.o server.o procopen.o
> fixlib.o fixopts.o ../libiberty/libiberty.a
What version of gcc do you have?
Can you do "gcc -v"? This has to be a bug with glibc.
--
--- Comment #6 from phorgan1 at gmail dot com 2008-05-28 04:54 ---
Subject: Re: gcc-4.3.0 build fails with multiple definitions
pinskia at gcc dot gnu dot org wrote:
> What version of gcc do you have?
> Can you do "gcc -v"? This has to be a bug with glibc.
>
Using built-in specs.
T
--- Comment #7 from ubizjak at gmail dot com 2008-05-28 05:45 ---
Fixed?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32000
Attached sample (reduced from glibc cvs) caused gcc built from latest
gcc-4_3-branch to ICE on arm. It worked ok with gcc 4.2.2. If I removed
-frename-registers then the ICE would not happen.
Steps to reproduce
Compile as follows
arm-none-linux-gnueabi-gcc -c -O2 sample.c -frename-registers
sam
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
CC||pinskia at gcc dot gnu dot
|
29 matches
Mail list logo
