Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] Fwd: [LLVMbugs] [Bug 1971] New: EQUIVALENCE not supported in llvm-gfortran"
2008 Feb 02
0
[LLVMdev] Fwd: [LLVMbugs] [Bug 1971] New: EQUIVALENCE not supported in llvm-gfortran
Vikram,
> I didn't know that EQUIVALENCE is the only unsupported major Fortran
> feature, as this bug says. Can you give me an update on the status of
> the Fortran front-end and what the near-term goals are?
Ok. I was going to post something soon after 2.2 release, but let's do
it now.
LLVM 2.2 will contain (as a part of llvm-gcc 4.2) a port of gfortran
compiler to the LLVM
2004 Oct 13
0
[LLVMdev] RESOLVED: [LLVMbugs] [Bug 451] Libtool does not create libNAME.$(SHLIBEXT) files when building dynamic libs
I'm forwarding this bug resolution because it has a pretty wide impact on LLVM
developers. This bug (451) has been resolved (well, works for me anyway). If
you have reconfigured your build tree since October 4th, you need to
reconfigure again. The bug produced shared objects that don't have a .so
extension. Reconfiguring will fix this problem. The notes below show what was
needed to
2012 Nov 09
1
[LLVMdev] LLVMbugs list suggestion
Currently the LLVMbugs list only receives emails when a new bug is
filed or an existing bug gets finally resolved. The gcc-bugs list on the
other hand receives an email for every new comment in bugzilla. This
leads to much better transparency, because you can easily see which bugs
are currently being worked on; while the current LLVMbugs setup left you
totally in the dark.
So my suggestion would
2016 Apr 29
2
XDEBUG build bots?
Thanks for noticing this, Geoff.
I just landed r268050 which add a cmake option for this (and unifies XDEBUG
and EXPENSIVE_CHECKS). This might make it easier to setup some build bots.
Thank you,
Filipe
On Fri, Apr 22, 2016 at 8:40 PM, Geoff Berry via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Bugs filed:
> 27488 <https://llvm.org/bugs/show_bug.cgi?id=27488> librarie
2006 Aug 31
0
[LLVMdev] gfortran
On Wed, 30 Aug 2006, Michael McCracken wrote:
> Hi, in a thread this afternoon about compiling the Fortran SPEC2000 to
> LLVM bytecode, Chris mentioned that it should be possible to compile
> to LLVM with the gfortran front end, although no one has necessarily
> tried it.
Yup.
> I was surprised (and happy) to hear this, as under the impression that
> it would require a
2011 Apr 09
0
[LLVMdev] dragonegg/llvm-gfortran/gfortran benchmarks
On Sat, Apr 09, 2011 at 08:56:49AM -0600, Marcus G. Daniels wrote:
> On 4/9/2011 6:09 AM, Duncan Sands wrote:
> > Hi Jack, thanks for the numbers. Any chance of analysing why gcc does better on
> > those where it does much better than dragonegg?
> >
> > Ciao, Duncan.
> Also, does -fplugin-arg-dragonegg-enable-gcc-optzns get Dragonegg to
> match GCC performance
2011 Apr 09
0
[LLVMdev] dragonegg/llvm-gfortran/gfortran benchmarks
Hi Jack, thanks for the numbers. Any chance of analysing why gcc does better on
those where it does much better than dragonegg?
Ciao, Duncan.
> With the case-insensitive file system patch from http://llvm.org/bugs/show_bug.cgi?id=9656#c15
> applied to dragonegg 2.9, the following Polyhedron 2005 benchmarks are seen on x86_64-apple-darwin10
> under gcc 4.5.3svn using the dragonegg
2008 Jun 20
0
[LLVMdev] llvm-gfortran polyhedron 2005 results [corrected]
The previously posted benchnarks for gcc vs
llvm-gfortran had one mistake. I was actually had
the gfortran for 4.3.1 installed instead of that
from gcc 4.2.4. Below are the polyhedron benchmark
results for all three compilers...
gfortran 4.2.4
Benchmark Compile Executable Ave Run Number Estim
Name (secs) (bytes) (secs) Repeats Err %
--------- -------
2007 Dec 27
0
[LLVMdev] llvm-gcc-4.2 and gfortran
Hello, Jack.
> the libgfortran directory. Thanks in advance for any
> information as I am working on test fink packaging for
> llvm-gcc42.
The gfortran is more or less ok nowadays. There are few patches waiting
in my queue, but I'll commit them soon. It seems, that llvm-gfortran can
compile almost all SPEC and polyhedron (there are few known issues,
though).
Unfortunately, I
2007 Dec 27
0
[LLVMdev] llvm-gcc-4.2 and gfortran
Hello, Jack
> and these are currently at revision 45366. Are these the same sources that you
> are using?
I've just commited remaining gfortran patches, which were in my queue.
So, last rev. seems to be 45366
> Lastly, are there any issues with running the gcc testsuite
> within the llvm-gcc-4.2 directories that I should be aware of?
I'm not aware about result of running
2009 Jan 25
1
[LLVMdev] gfortran benchmarks
Since the fact that gfortran performance has improved
over the major releases, I decided to benchmark the current
releases on a MacPro with the Polyhedron 2005 benchmarks
using -ffast-math -funroll-loops -msse3 -O3. The results
are...
gcc release
gcc 4.2.4 gcc 4.3.3 gcc 4.4-pre gcc 4.3.3/ gcc 4.4-pre/
2008 Nov 03
0
[LLVMdev] llvm-gfortran gives errors on AMD64-Ubuntu
Hi,
> I have installed llvm and llvm-gfortran on Pentium4 machine using 32-bit
> Ubuntu, it works fine. I recently installed them on AMD64-Ubuntu 8.04,
> llvm-gfortran gave me following errors
>
> $ llvm-gfortran -Wall hello.f95 -o hellof
this works here on x86-64 ubuntu 8.10. I took a look in my libgfortran.a
and it doesn't reference any of the symbols you mention.
>
2011 Apr 09
2
[LLVMdev] dragonegg/llvm-gfortran/gfortran benchmarks
With the case-insensitive file system patch from http://llvm.org/bugs/show_bug.cgi?id=9656#c15
applied to dragonegg 2.9, the following Polyhedron 2005 benchmarks are seen on x86_64-apple-darwin10
under gcc 4.5.3svn using the dragonegg plugin...
================================================================================
Date & Time : 8 Apr 2011 19:52:56
Test Name :
2007 May 02
1
[LLVMdev] [LLVMbugs] Anyone seeing this?
> Anyone seeing this failure?
>
> FAIL: /Volumes/Gir/devel/llvm/llvm.src/test/CodeGen/Generic/2007-04-14-EHSelectorCrash.ll
> for PR1326
Seems it was due to my changes. Investigating.
--
With best regards, Anton Korobeynikov.
Faculty of Mathematics & Mechanics, Saint Petersburg State University.
2007 Dec 22
0
[LLVMdev] [LLVMbugs] Compiling to Win32
Hello, Tom
> * Intel and AMD machines running on Win32 using MinGW libraries
> (native)
As you can see here, LLVM is happy on win32.
> without installing third-party libraries? Do these libraries need to
> be distributed along with the generated executables?
It depends on, how exactly you're compiling LLVM. If you'll go with
Cygwin-generated binaries, then yes
2008 Jan 04
1
[LLVMdev] [LLVMbugs] [Bug 1896] New: Global Variable Optimizer fails assertion in OptimizeAwayTrappingUsesOfLoads
It looks like something has gotten its clock off by 12 hours; this
arrived at 5:37 PM local time,
and the clock on my local machine is correct...
On Jan 3, 2008, at 5:37 AM, bugzilla-daemon at cs.uiuc.edu wrote:
> http://llvm.org/bugs/show_bug.cgi?id=1896
>
> Summary: Global Variable Optimizer fails assertion in
> OptimizeAwayTrappingUsesOfLoads
2010 Feb 22
0
[LLVMdev] llvmbugs mailing list going crazy
Hi All,
I did something dumb and bugzilla is sending out a ton of spam. We're working on it, I apologize for the email!
-Chris
2008 Jun 13
0
[LLVMdev] gfortran bugs filed
I've filed bugzilla reports for the gcc 4.2.1 gfortran
testsuite failures in llvm/llvm-gcc-4.2 v2.3. These are...
http://llvm.org/bugs/show_bug.cgi?id=2430
http://llvm.org/bugs/show_bug.cgi?id=2431
http://llvm.org/bugs/show_bug.cgi?id=2437
http://llvm.org/bugs/show_bug.cgi?id=2438
http://llvm.org/bugs/show_bug.cgi?id=2439
http://llvm.org/bugs/show_bug.cgi?id=2440
2008 Nov 01
2
[LLVMdev] llvm-gfortran gives errors on AMD64-Ubuntu
Hi,
I have installed llvm and llvm-gfortran on Pentium4 machine using 32-bit
Ubuntu, it works fine. I recently installed them on AMD64-Ubuntu 8.04,
llvm-gfortran gave me following errors
$ llvm-gfortran -Wall hello.f95 -o hellof
/home/jli127/LLVM/llvm-gcc/install/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.2.1/../../../../lib64/libgfortran.a(error.o):
In function `_gfortrani_gfc_itoa':
2010 Apr 08
0
[LLVMdev] darwin llvm-gfortran Polyhedron 2005 results
On Apr 7, 2010, at 8:41 PM, Jack Howarth wrote:
> Building the current release 2.7 branch on x86_64-apple-darwin10
> with r81455 reverted, I get the following Polyhedron 2005 benchmark
> results (with no test failures)...
Very nice! A 14% speedup on a benchmark we don't tune for isn't bad. I imagine that there are several easy wins you could get on it if you were interested