On Mon, Apr 07, 2025 at 02:42:10PM +0800, Gwen Fu wrote:
> Thanks for your reply !
> >The word "parameter" has very a specific meaning in Fortran. The
> >entity that is passed into a function or subroutine is an "actual
> >argument". The entity within the functions associated with the
> >"actual ar
On Sat, Apr 05, 2025 at 03:16:45PM +0800, Gwen Fu wrote:
> My doubt :
> 1.Does the compilation option only need to support fortran versions above
> 9, o5r does it also need to support fortran 77?
gfortran started life as a Fortran 95 compiler. It should
support anything that is Fortran 95 or late
On Wed, Nov 13, 2024 at 05:33:20PM +0100, Thomas Koenig wrote:
> Am 13.11.24 um 15:55 schrieb Toon Moene:
> >
> > Since the Fortran 95 Standard it does (in the current Standard: 7.4.3.2
> > Real type):
> >
> > The real type includes a zero value. Processors that distinguish between
> > positive a
On Sat, Feb 10, 2024 at 07:35:22PM +0100, Marc Glisse wrote:
> On Sat, 10 Feb 2024, Steve Kargl via Gcc wrote:
>
> > So, how does one biulding all parts of gcc with "-O -g"?
> >
> > In my shell script, I have
> >
> > CFLAGS="-O -g"
> &g
So, how does one biulding all parts of gcc with "-O -g"?
In my shell script, I have
CFLAGS="-O -g"
export CFLAGS
CXXFLAGS="-O -g"
export CXXFLAGS
BOOT_CFLAGS="-O -g"
export BOOT_CFLAGS
../gcc/configure --prefix=$HOME/work --enable-languages=c,c++,fortran \
--enable-bootstrap --disable-libssp
On Tue, Jan 31, 2023 at 10:38:02PM +0800, LIU Hao wrote:
> 在 2023-01-31 21:13, Thomas Schwinge 写道:
> > Hi!
> >
> > On 2023-01-30T14:50:08-0800, Steve Kargl via Fortran
> > wrote:
> > > Does the skull and crossbones convey anymore info tha
On Mon, Jan 30, 2023 at 11:07:46PM +0100, Gerald Pfeifer wrote:
> On Mon, 30 Jan 2023, Steve Kargl via Gcc wrote:
> > Bingo. In the case of non-[a-zA-Z] characters in the
> > Subject (or Fromi or To) line, the spam folder is normally
> > named /dev/null.
>
> Hmm, so
On Mon, Jan 30, 2023 at 03:46:30PM +0100, Thomas Koenig wrote:
> On 30.01.23 14:52, Mark Wielaard wrote:
> > Hi Steve,
> >
> > On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote:
> > > Please remove the skull and cross bones in the subject line.
> &
On Sun, Jan 29, 2023 at 07:49:35PM +, Sam James via Fortran wrote:
>
>
> > On 29 Jan 2023, at 19:36, Jerry D via Gcc wrote:
> >
> > I had this show up today. I have no idea what this is about.
> >
> > Please advise.
> >
>
> Sorry Jerry, false positive -- something went wrong with
> the b
On Tue, Apr 12, 2022 at 06:42:20PM +0100, Jonathan Wakely wrote:
> On Tue, 12 Apr 2022 at 18:32, Steve Kargl wrote:
> > Well, I determined what the problem is. On FreeBSD,
> > GNU make is gmake. make(1) on FreeBSD is BSD make.
> >
> > % gmake -j7 check-c
> >
&
On Tue, Apr 12, 2022 at 09:26:58AM +0200, Richard Biener wrote:
> On Tue, Apr 12, 2022 at 9:07 AM Richard Biener
> wrote:
> >
> > On Tue, Apr 12, 2022 at 1:53 AM Steve Kargl via Gcc wrote:
> > >
> > > If I configure gcc with the following
> > >
If I configure gcc with the following
../gccx/configure --prefix=$HOME/work/x --enable-languages=c,c++,fortran \
--enable-bootstrap --disable-nls --enable-checking --disable-multilib \
--disable-libsanitizer --disable-lto.
then bootstrap gcc, why do I see 1000s of failures with
% cd gcc
% gm
On Mon, Sep 30, 2019 at 08:51:51PM -0700, Steve Kargl wrote:
>
> Can you just zero memory and remove the explicit setting
> of the terminating '\0'?
>
> q = buffer;
> memset(q, 0, len);
>
(may be dup)
Upon further reading of the code, does buffer have
8*len+
On Mon, Sep 30, 2019 at 08:40:29PM -0700, Jerry DeLisle wrote:
> Copying gcc list for additional thoughts on a possible bogus warning.
>
> On 9/29/19 9:02 AM, Jerry DeLisle wrote:
> > Hi all,
> >
> --- snip ---
>
> > diff --git a/libgfortran/io/write.c b/libgfortran/io/write.c
> > index 4ef35561
On Thu, Sep 05, 2019 at 07:08:48AM -0700, Steve Kargl wrote:
> On Thu, Sep 05, 2019 at 07:03:25AM -0700, Steve Kargl wrote:
> > On Thu, Sep 05, 2019 at 02:16:08PM +0300, Janne Blomqvist wrote:
> > > On Thu, Sep 5, 2019 at 2:08 PM Nathan Sidwell wrote:
> > > >
&
On Thu, Sep 05, 2019 at 07:03:25AM -0700, Steve Kargl wrote:
> On Thu, Sep 05, 2019 at 02:16:08PM +0300, Janne Blomqvist wrote:
> > On Thu, Sep 5, 2019 at 2:08 PM Nathan Sidwell wrote:
> > >
> > > Is it time to deprecate traditional preprocessing? It's been 30
On Thu, Sep 05, 2019 at 02:16:08PM +0300, Janne Blomqvist wrote:
> On Thu, Sep 5, 2019 at 2:08 PM Nathan Sidwell wrote:
> >
> > Is it time to deprecate traditional preprocessing? It's been 30 years
> > since C89. Are (non-compiler) tools that use it still things?
> >
> > Handling it gets its ho
On Tue, Aug 20, 2019 at 09:56:27PM +0200, Thomas Koenig wrote:
> I wrote:
>
> > Committed as r274551.
>
> Well, this revision appears to have woken quite a few bugs from their
> slumber. While argument mismatch was always illegal, it seems to have
> been a common idiom at one time. And, like al
On Sat, May 25, 2019 at 02:52:53PM +0200, Thomas Koenig wrote:
>
> consider this: There is a bug, confirmed by several people. This occurs
> in closed-source, proprietary software, and appears to be due to one
> of my commits.
>
> Despite considerable help from somebody who has access to the sour
On Tue, Mar 12, 2019 at 12:15:01PM +0100, Martin Liška wrote:
> On 3/11/19 6:23 PM, Steve Kargl wrote:
> > On Mon, Mar 11, 2019 at 12:07:55PM -0400, David Malcolm wrote:
> >> On Mon, 2019-03-11 at 15:18 +0100, Martin Liška wrote:
> >>> Hi.
> >>>
> &
On Mon, Mar 11, 2019 at 12:07:55PM -0400, David Malcolm wrote:
> On Mon, 2019-03-11 at 15:18 +0100, Martin Liška wrote:
> > Hi.
> >
> > I would like to add %' into __gcc_gfc__ in order to handle:
> >
> > ./xgcc -B. /tmp/module.ii -Wformat -c
> > /home/marxin/Programming/gcc/gcc/fortran/module.c:
On Sun, Jan 27, 2019 at 01:19:08PM -0800, Andrew Pinski wrote:
> On Sun, Jan 27, 2019 at 1:02 PM Thomas König wrote:
> >
> > Am 27.01.19 um 21:52 schrieb Steve Kargl:
> >
> > > In fact, I would be in favor of removing -Wall, as it is misnamed,
> > > in
On Sun, Jan 27, 2019 at 08:34:57PM +, Jonathan Wakely wrote:
> On Sun, 27 Jan 2019 at 13:56, N.M. Maclaren wrote:
> >
> > So I think that there is a strong argument for such an option in gfortran,
> > irrespective of whether there is for gcc and g++.
>
> Then -Wall should enable them for Fort
On Sun, May 20, 2018 at 07:27:06AM +0200, Richard Biener wrote:
> On May 20, 2018 7:20:25 AM GMT+02:00, Steve Kargl
> wrote:
> >So, there is a P1 blocking bootstrap failure on trunk.
> >I've opened a PR and finally had time to locate the
> >offending commit.
> &
So, there is a P1 blocking bootstrap failure on trunk.
I've opened a PR and finally had time to locate the
offending commit.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
As I cannot bootstrap gcc, I cannot test a set of
patches for gfortran that I have in my tree nor
identify which recent
I added some documentation to fortran/intrinsic.texi. In
processing the gfortran.f90, I discovered this warning.
makeinfo --split-size=500 --split-size=500 --split-size=500 \
-I ../../gcc/gcc/doc/include -I ../../gcc/gcc/fortran \
-o doc/gfortran.info ../../gcc/gcc/fortran/gfo
On Fri, Nov 03, 2017 at 12:41:30PM -0600, Jeff Law wrote:
> On 11/03/2017 12:34 PM, Steve Kargl wrote:
> > One of the tests for gfortran has been XPASSing
> > on newer versions of FreeBSD. The testcase has
> > the line
> >
> > ! { dg-xfail-if "" { &q
One of the tests for gfortran has been XPASSing
on newer versions of FreeBSD. The testcase has
the line
! { dg-xfail-if "" { "*-*-freebsd*" } { "*" } { "" } }
I know the tests passes on *-*-freebsd12.0. I should
pass on *-*-freebsd11.* and perhaps *-*-freebsd10.*.
I don't know if it passes on
On Tue, Apr 25, 2017 at 06:58:56PM +0200, Jakub Jelinek wrote:
> On Tue, Apr 25, 2017 at 09:54:04AM -0700, Steve Kargl wrote:
> > On Tue, Apr 25, 2017 at 05:46:15PM +0200, Andreas Schwab wrote:
> > > On Apr 25 2017, Steve Kargl wrote:
> > >
> > > > Someon
On Tue, Apr 25, 2017 at 06:58:56PM +0200, Jakub Jelinek wrote:
> On Tue, Apr 25, 2017 at 09:54:04AM -0700, Steve Kargl wrote:
> > On Tue, Apr 25, 2017 at 05:46:15PM +0200, Andreas Schwab wrote:
> > > On Apr 25 2017, Steve Kargl wrote:
> > >
> > > > Someon
On Tue, Apr 25, 2017 at 05:46:15PM +0200, Andreas Schwab wrote:
> On Apr 25 2017, Steve Kargl wrote:
>
> > Someone (other than Richard who seems to have fixed his
> > bootstrap issue) in the last 3 days has broken bootstrap
> > on FreeBSD.
>
> Did you change your
On Tue, Apr 25, 2017 at 04:13:45PM +, Joseph Myers wrote:
> On Tue, 25 Apr 2017, David Malcolm wrote:
>
> > >From what I can tell, the n_opts and opts in that file come direct from
> > opt-read.awk, which gets them from opt-gather.awk, which appears to
> > sort them (but my awk skills are wea
On Tue, Apr 25, 2017 at 11:09:05AM -0400, David Edelsohn wrote:
> >
> > From what I can tell, the n_opts and opts in that file come direct from
> > opt-read.awk, which gets them from opt-gather.awk, which appears to
> > sort them (but my awk skills are weak).
> >
> > Alternatively, maybe the colli
Someone (other than Richard who seems to have fixed his
bootstrap issue) in the last 3 days has broken bootstrap
on FreeBSD. The generated file gcc/options.h contains
code of the form
OPT_C = 116, /* -C */
OPT_CC = 117, /* -CC */
OP
On Mon, Mar 27, 2017 at 07:41:12PM +0200, Marek Polacek wrote:
> On Mon, Mar 27, 2017 at 07:33:05PM +0200, Toon Moene wrote:
> > On 03/27/2017 06:45 PM, Marek Polacek wrote:
> >
> > > On Mon, Mar 27, 2017 at 09:27:34AM -0700, Steve Kargl wrote:
> >
> > > &g
On Mon, Mar 27, 2017 at 06:45:32PM +0200, Marek Polacek wrote:
> On Mon, Mar 27, 2017 at 09:27:34AM -0700, Steve Kargl wrote:
> > On Mon, Mar 27, 2017 at 05:22:12PM +0200, Markus Trippelsdorf wrote:
> > > On 2017.03.27 at 06:49 -0700, Steve Kargl wrote:
> > > >
&
On Mon, Mar 27, 2017 at 05:22:12PM +0200, Markus Trippelsdorf wrote:
> On 2017.03.27 at 06:49 -0700, Steve Kargl wrote:
> >
> > Go scan the gcc-patches mailing list for "fallthrough". I'll
> > note other have concerns. Here's one example:
> >
On Mon, Mar 27, 2017 at 03:39:37PM +0200, Markus Trippelsdorf wrote:
>
> Well, a missing break is a bug. No?
Every 'case' statement without exception must be accompanied by
a 'break' statement? Wasting others' time to "fix" working
correct code is acceptable?
--
Steve
20161221 https://www.yout
On Mon, Mar 27, 2017 at 02:36:27PM +0100, Jonathan Wakely wrote:
> On 27 March 2017 at 14:26, Steve Kargl wrote:
> > I completely disagree with your viewpoint here. If someone turns
> > on a silly warning, that someone should fix all places within the
> > tree that triggers
On Mon, Mar 27, 2017 at 08:58:43AM +0200, Markus Trippelsdorf wrote:
> On 2017.03.26 at 19:30 -0700, Steve Kargl wrote:
> > On Sun, Mar 26, 2017 at 06:45:07PM -0700, Jerry DeLisle wrote:
> > > On 03/26/2017 11:45 AM, Steve Kargl wrote:
> > > > On Sun, Mar 26, 2
On Sun, Mar 26, 2017 at 06:45:07PM -0700, Jerry DeLisle wrote:
> On 03/26/2017 11:45 AM, Steve Kargl wrote:
> > On Sun, Mar 26, 2017 at 11:27:59AM -0700, Jerry DeLisle wrote:
> >>
> >> +#pragma GCC diagnostic push
> >> +#pragma GCC diagnostic ignored "-Wi
Hi,
If I run configure with "--program-suffix=6", I get gcc6, gfortran6, etc.
When ldd looks for libgcc.so.1 on FreeBSD, she finds the wrong one.
% cat foo.f90
program foo
print *, 'Hello'
end program
% gfortran6 -o z foo.f90 && ./z
/lib/libgcc_s.so.1: version GCC_4.6.0 required by \
/usr/loca
On Mon, Nov 16, 2015 at 12:04:06AM +0100, Thomas Koenig wrote:
> See
>
> http://arstechnica.com/information-technology/2015/11/llvm-to-get-fortran-compiler-that-targets-parallel-gpus-in-clusters/
>
> It is not entirely clear on what they plan to do.
>
> Use gfortran via dragonegg?
>
The 3 DOE
On Wed, Oct 14, 2015 at 11:48:27AM -0400, Tim Prince wrote:
>
> >
> > I added gcc@gcc.gnu.org as this technically isn't a Fortran issue.
> test suite reports hundred of new ICE instances, all referring to this
> seh_unwind_emit function:
>
> /cygdrive/c/users/tim/tim/tim/src/gnu/gcc1/gcc/testsuit
On Wed, Oct 14, 2015 at 11:32:52AM -0400, Tim Prince wrote:
>
> Sorry if someone sees this multiple times; I think it may have been
> stopped by ISP or text mode filtering:
>
> Since Sept. 26, the partial support for Windows 64-bit has been dropped
> from gcc trunk:
> winnt.c apparently has probl
There appears to be a missed opportunity to optimize
away exponential operators. I suspect that this
falls under gfortrani's frontend-optimize option, but
it may also be a middle-end issue.
Consider,
subroutine foo(n)
integer n
integer i, j
i = 2
j = 4
n = i**j ! <-- Th
On Sun, Sep 21, 2014 at 10:15:01PM -0700, Andrew Pinski wrote:
> On Sun, Sep 21, 2014 at 8:08 PM, Steve Kargl
> wrote:
> > On Sun, Sep 21, 2014 at 07:57:45PM -0700, Andrew Pinski wrote:
> >> On Sun, Sep 21, 2014 at 6:56 PM, Steve Kargl
> >> wrote:
> >>
On Sun, Sep 21, 2014 at 07:57:45PM -0700, Andrew Pinski wrote:
> On Sun, Sep 21, 2014 at 6:56 PM, Steve Kargl
> wrote:
> > + is a binary operator. 0x3ffe is a hexidecimal-constant according
> > to 6.6.4.1 in n1256.pdf. 63 is, of course, a decimal-constant.
>
>
> T
On Sun, Sep 21, 2014 at 10:49:53PM -0400, Ed Smith-Rowland wrote:
> On 09/21/2014 09:56 PM, Steve Kargl wrote:
> > + is a binary operator. 0x3ffe is a hexidecimal-constant according
> > to 6.6.4.1 in n1256.pdf. 63 is, of course, a decimal-constant.
> >
> Also, a hex flo
+ is a binary operator. 0x3ffe is a hexidecimal-constant according
to 6.6.4.1 in n1256.pdf. 63 is, of course, a decimal-constant.
--
steve
On Sun, Sep 21, 2014 at 06:49:54PM -0700, Andrew Pinski wrote:
> On Sun, Sep 21, 2014 at 6:23 PM, Steve Kargl
> wrote:
>
> No e+ is exp
#include
#include
int
main(void)
{
uint16_t i;
i = 0x3ff0+63; printf("%x\n", i);
i = 0x3ff1+63; printf("%x\n", i);
i = 0x3ff2+63; printf("%x\n", i);
i = 0x3ff3+63; printf("%x\n", i);
i = 0x3ff4+63; printf("%x\n", i);
i = 0x3ff4+63; printf("
On Fri, Jun 06, 2014 at 10:07:37PM +0200, FX wrote:
> In fortran/trans-decl.c, we have a comment above the code building function
> decls, saying:
>
>>The SPEC parameter specifies the function argument and return type
>>specification according to the fnspec function type attribute. */
>
On Mon, Nov 04, 2013 at 09:58:30PM +0100, Tobias Burnus wrote:
> Tobias Burnus wrote:
> > Gerald Pfeifer wrote:
> >> To make it easier to reproduce builds of software and entire GNU/Linux
> >> distributions, RMS had the idea of adding a warning to GCC that warns
> >> about the use of __DATE__ and _
On Sat, Aug 04, 2012 at 09:37:10AM -0700, H.J. Lu wrote:
> Hi,
>
> I saw massive FORTRAN failures on trunk with both SPEC CPU 2006
> and GCC FORTRAN testsuite. Is this a known problem? Should I open a bug
> report?
>
It is difficult to know whether this is a known problem
given that you failed
On Wed, Jan 18, 2012 at 08:34:41PM +0100, Thomas Koenig wrote:
> Hello,
>
> I have set up a semi-automatic lapack tester on
> powerpc64-unknown-linux-gnu (gcc110 on the gcc compile farm).
> It downloads the current trunk, compiles it, then uses that
> compiler to compile the reference BLAS and Lap
With top of tree, I'm seeing
% ../gcc4x/configure --prefix=$HOME/work --enable-languages=c,fortran \
--disable-libmudflap --disable-bootstrap
% gmake
libtool: compile: g++ -B/usr/home/kargl/work/i386-unknown-freebsd10.0/bin/
-B/usr/home/kargl/work/i386-unknown-freebsd10.0/lib/ -isystem
/usr/hom
On Sat, Aug 06, 2011 at 03:16:43PM +0200, Toon Moene wrote:
> On 08/06/2011 11:22 AM, Mikael Morin wrote:
>
> >WRT to bootstrap time, as usual: it's too long.
>
> Well, that all depends on your (time) frame of reference, of course. In
> the summer months leading up to Craig Burley asking for vo
On Fri, Aug 05, 2011 at 06:51:12PM -0700, Ian Lance Taylor wrote:
> Thomas Koenig writes:
>
> > I just noticed that C++ now appears to be built by default, even when
> > only the C and fortran are specified. The configure line
> >
> >
> > ../trunk/configure --prefix=$HOME --enable-languages=c,f
On Sat, Aug 06, 2011 at 12:52:02AM +0200, Thomas Koenig wrote:
> Hello world,
>
> I just noticed that C++ now appears to be built by default, even when
> only the C and fortran are specified. The configure line
>
>
> ../trunk/configure --prefix=$HOME --enable-languages=c,fortran
> --with-mpc
On Sun, Jun 19, 2011 at 11:04:09PM +0700, "C. Bergstr?m" wrote:
>
>
> I can't say I really care about Andy's alleged copyright infringement.
> (My general point on matters like this is litigate or shut up. We're
> all here to get work done and licensing (licensing trolls and I don't
> mean y
On Sun, Jun 19, 2011 at 12:13:25AM +0700, "C. Bergstr?m" wrote:
> On 06/18/11 11:41 PM, Steve Kargl wrote:
> >Good luck with that endeavor. After the gfortran fork,
> >a certain individual would routinely obfusicate the code
> >in one of the repositories via gratu
On Sat, Jun 18, 2011 at 06:22:21PM +0700, Christopher Bergstr?m wrote:
> 2011/6/18 Toon Moene :
> > On 06/18/2011 01:02 PM, "C. Bergstr?m" wrote:
> >> On 06/18/11 05:16 PM, Toon Moene wrote:
> >>> On 06/18/2011 12:12 PM, Toon Moene wrote:
> On 06/18/2011 05:05 AM, Christopher Bergstr?m wrote:
On Sun, Sep 26, 2010 at 04:47:29PM +0200, Tobias Burnus wrote:
> Hello all,
>
> given the optimization work which has gone into 4.6, I thought I would
> run the Polyhedron Fortran test suite.
I was interested in seeing how 4.6 stacks up against previous
versions of gfortran. On x86_64-*-freebs
On Sat, Sep 25, 2010 at 10:46:32AM +0200, Jakub Jelinek wrote:
> On Fri, Sep 24, 2010 at 10:44:54PM -0700, Steve Kargl wrote:
> > So, with the new bugzilla, how does one confirm a bug
> > is a bug? If I click on the button next to the
> > "status:" field, the se
So, with the new bugzilla, how does one confirm a bug
is a bug? If I click on the button next to the
"status:" field, the selections listed are unconfirmed,
new, assigned, suspended, waiting, and resolved. Where's
the confirm selection?
--
Steve
On Sat, Sep 11, 2010 at 01:05:23AM +0200, Angelo Graziosi wrote:
> Il 10/09/2010 19.31, Steve Kargl ha scritto:
> >The ideal solution would be incorporating libquad into libgfortran
>
> The ideal solution would be building GCC enabling QP with
>
> ./configure... --enable
On Fri, Sep 10, 2010 at 07:08:10PM +0200, FX wrote:
> I'm CC'ing the gcc list so I can get insight from people who understand
> correctly how static libraries should be handled by the driver...
>
> > I'm seeing a similar issue with -static linkage.
> >
> > % gfc4x -o z norm2_3.f90 -L/usr/home/sg
On Mon, Aug 30, 2010 at 03:29:20PM -0700, Steve Kargl wrote:
> On Mon, Aug 30, 2010 at 09:51:09PM +0200, Uros Bizjak wrote:
> >
> > So, attached and untested.
> >
> > Uros.
>
> I tested your patch on x86_64-*-freebsd. My ppl and cloog
> libraries were bu
On Mon, Aug 30, 2010 at 09:51:09PM +0200, Uros Bizjak wrote:
>
> So, attached and untested.
>
> Uros.
I tested your patch on x86_64-*-freebsd. My ppl and cloog
libraries were built with FreeBSD's system gcc (4.2.1). All
tests failed due to missing symbols that are marked GCC_3.0.
> Index: gcc
On Mon, Aug 30, 2010 at 08:28:58AM +0200, Uros Bizjak wrote:
>
> Oh, additional patch for libgcc is also needed. Attached patch will
> enable filtering out TImode on 32bits and will also enable fallbacks
> for the two missing functions, so no need for any other changes.
>
> Can you please regress
On Sun, Aug 29, 2010 at 10:48:46PM +0200, Uros Bizjak wrote:
> Hello!
>
> > On Sun, Aug 29, 2010 at 09:01:49AM +0200, FX wrote:
> > > GCC >= 4.5 is needed. I'll add a check to libquad's configure.
> > >
> > > FX
> > >
> >
> > Further testing on i386-*-freebsd runs into undefined symbols.
> >
>
On Sun, Aug 29, 2010 at 09:01:49AM +0200, FX wrote:
> GCC >= 4.5 is needed. I'll add a check to libquad's configure.
>
> FX
>
Further testing on i386-*-freebsd runs into undefined symbols.
libquad.so: undefined reference to `__getf2'
libquad.so: undefined reference to `__eqtf2'
libquad.so: unde
On Sat, Aug 28, 2010 at 05:56:57PM -0700, Steve Kargl wrote:
> On Sat, Aug 28, 2010 at 05:47:28PM -0700, Steve Kargl wrote:
> > On Sun, Aug 29, 2010 at 01:24:47AM +0200, FX wrote:
> > > Before I submit it officially for review, I want this patch to get some
> > > expo
On Sat, Aug 28, 2010 at 05:47:28PM -0700, Steve Kargl wrote:
> On Sun, Aug 29, 2010 at 01:24:47AM +0200, FX wrote:
> > Before I submit it officially for review, I want this patch to get some
> > exposure while I clean up a few remaining dusty corners. To test the patch
>
On Sun, Aug 29, 2010 at 01:24:47AM +0200, FX wrote:
> Before I submit it officially for review, I want this patch to get some
> exposure while I clean up a few remaining dusty corners. To test the patch on
> x86_64-linux, proceed as follows:
>
> -- Get libquad from http://quatramaran.ens.fr/~c
On Sat, Aug 14, 2010 at 12:08:21AM +0200, Tobias Burnus wrote:
>
> In terms of options, I think -funroll-loops should also be used as it
> usually improves performance (it is not enabled by any -O... option).
>
I wonder if gfortran should check if -O and -O2 is given,
and then add -funroll-loop
On Thu, Aug 12, 2010 at 08:47:34PM +0200, Toon Moene wrote:
> Steve Kargl wrote:
>
> ># gfc4x 9.814 9.358 8.622 9.810 Note1 9.172 8.958 9.022
>
> Column 5 compiled with -march=native -O2 -ffast-math
>
> ># Note 1: STOP DLAMC1 failure (10)
>
> T
On Thu, Aug 12, 2010 at 09:51:42AM +0200, Steven Bosscher wrote:
> On Thu, Aug 12, 2010 at 8:46 AM, Ralf W. Grosse-Kunstleve
> wrote:
> > Hi Vladimir,
> >
> > Thanks for the feedback! Very interesting.
> >
> >
> >> Intel optimization compiler team (besides researchers) is much bigger than
> >>whol
Kai,
I tested your patch posted here:
http://gcc.gnu.org/ml/gcc/2010-05/msg00445.html
to address the issue
% cat x.c
int main() { }
% gccvs -flto x.c
% gccvs -fwhopr x.c
lto1: fatal error: elf_update() failed: Layout constraint violation
compilation terminated.
lto-wrapper
On Sat, May 22, 2010 at 11:07:44PM +0200, Richard Guenther wrote:
> On Sat, May 22, 2010 at 10:29 PM, Steve Kargl
> wrote:
> > Guys,
> >
> > I only read the gcc@ archive, so sorry about breaking the thread.
> > Testing with gfortran finds
> >
> > Free
Guys,
I only read the gcc@ archive, so sorry about breaking the thread.
Testing with gfortran finds
FreeBSD's libelf with no patches.
=== gfortran Summary ===
# of expected passes34177
# of unexpected failures40
# of expected failures 33
# of unreso
On Fri, Jun 26, 2009 at 06:51:35PM +0200, Angelo Graziosi wrote:
> Steve Kargl ha scritto:
> >
> >Can you guys learn to trim the cc list? This issue
> >has absoutely nothing to do with gfortran. Yet,
> >for...@gcc.gnu.org is being spammed with your email.
>
> Re
On Fri, Jun 26, 2009 at 06:17:15PM +0200, Kai Tietz wrote:
>
> you can find the binutils project as usual under
> http://sources.redhat.com/binutils/ . You can find on this page how
> you are able to get current cvs version of binutils. This project
> contains the gnu tools, like dlltool, as, objc
Someone has broken gfortran on FreeBSD with dwarf debugging.
This is a regression. Please fix!
Testing debug/trivial.f, -gdwarf-21
Executing on host: /usr/home/kargl/gcc/obj4x/gcc/testsuite/gfortran/../../gfortr
an -B/usr/home/kargl/gcc/obj4x/gcc/testsuite/gfortran/../../ /usr/home/kargl/gcc
/gcc
On Mon, Jun 01, 2009 at 12:49:42PM -0700, Janis Johnson wrote:
> On Mon, 2009-06-01 at 11:14 -0700, Steve Kargl wrote:
> >
> > If someone uses -fno-openmp and still tries to link to libgomp,
> > then the -pthread option is missing and hence the test fail
> > because -lp
On Mon, Jun 01, 2009 at 07:59:15PM +0200, Gerald Pfeifer wrote:
> Excess errors:
> /pfeifer/OBJ-0531-2252/i386-unknown-freebsd7.1/./libgomp/.libs/libgomp.so:
> undefined reference to `pthread_create'
>
> And what all of these three testcases have in common is
>
> { dg-options "-fno-openmp
On Sun, Apr 05, 2009 at 05:48:44PM +0200, Daniel Franke wrote:
> Hi all.
>
> Here's another spurious(?) uninitialized warning. As the full range is
> implied, the question is, if this a fortran or a middle-end problem:
>
> $> cat range.f90
> FUNCTION f(n)
> INTEGER, INTENT(in) :: n
> REAL
On Thu, Mar 19, 2009 at 07:46:37PM +0100, Toon Moene wrote:
>
> I agree about the bisecting-in-case-of-bugs issue.
>
> However, what I see happening in practice is that all GCC developers
> keep on doing their development work on branches - only the gfortran
> developers are left out, because th
On Sat, Jan 10, 2009 at 07:06:48PM +0100, Toon Moene wrote:
> L.S.,
>
> I have kept this under wraps for some weeks because I wanted to be sure
> all Steering Committee members had a chance to review this request - in
> spite of the holiday season.
>
> Now, however, I want to congratulate Danie
On Sat, Jan 03, 2009 at 08:11:14PM +0100, Richard Guenther wrote:
> On Sat, 3 Jan 2009, Toon Moene wrote:
>
> > [ Happy New Year first of all - hope we don't have too many more of them
> > ... Hey, you can recognize a Jimi Hendrix fan, don't you ]
>
> ;)
>
> > Richard Guenther wrote:
> >
> >
On Sun, Nov 30, 2008 at 10:18:22PM +0100, Richard Guenther wrote:
> On Sun, Nov 30, 2008 at 5:28 AM, Steve Kargl
> <[EMAIL PROTECTED]> wrote:
> >
> > ERRMSG.12 = &"Attempt to deallocate an unallocated object"[1]{lb: 1 sz:
> > 1};
> > -
First, I'll preface this with "I'm probably doing something wrong."
I'm adding support to gfortran for the ERRMSG argument to [DE]ALLOCATE.
Here's, some code to demonstrate:
program a
call works
call fails
end program a
!
! Work with all optimization levels.
!
subroutine works
character(l
On Sat, Nov 29, 2008 at 09:41:30PM +0100, Tobias Burnus wrote:
>
> I'm thinking about how to implement Fortran 2003's IEEE support in
> gfortran. The IEEE allow
> a) To set an IEEE value (NaN, INF, etc.)
> b) Check whether a value is NaN, etc.
> c) To query for IEEE capabilities (IEEE_SUPPORT_NAN,
On Wed, Nov 26, 2008 at 10:47:07AM -0500, Robert Dewar wrote:
> Steve Kargl wrote:
>
> >With regard to the top 10% performance, Absoft is simply comparing
> >the overall mean performance numbers from the Polyhedron Benchmark.
> >gfortran will never look good by that met
On Wed, Nov 26, 2008 at 01:55:01PM +0100, Mikael Morin wrote:
> Steve Kargl wrote:
> > Dear Absoft,
> >
> > Please fix the errors on your web page:
> >
> > http://www.absoft.com/Absoft_Windows_Compiler.htm
> >
> Do you really think they will change the
Dear Absoft,
Please fix the errors on your web page:
http://www.absoft.com/Absoft_Windows_Compiler.htm
The comparison chart is not only misleading, it is a down
right lie! The last column is labeled "GNU g77 gfortran".
g77 and gfortran are completely different compilers! gfortran
is a Fortran
On Wed, Sep 03, 2008 at 11:19:37AM -0700, Andrew Pinski wrote:
> On Wed, Sep 3, 2008 at 11:06 AM, Sebastian Pop <[EMAIL PROTECTED]> wrote:
> > On Tue, Sep 2, 2008 at 8:42 PM, Tobias Grosser
> > <[EMAIL PROTECTED]> wrote:
> >> It seems this code is already there, but the check for
> >> "check_effect
On Tue, Sep 02, 2008 at 06:38:03PM -0300, Tobias Grosser wrote:
>
> The necessary libraries are described here:
>
> http://gcc.gnu.org/wiki/Graphite
>
Grabbing PPL is fairly easy because a tarball is available.
Cloog OTOH hand is a pain in the ass to obtain bacause I
don't have git installed.
On Tue, Sep 02, 2008 at 06:15:56PM -0300, Tobias Grosser wrote:
> Hi Steve,
> On Tue, 2008-09-02 at 13:59 -0700, Steve Kargl wrote:
> >
> > gfortran.log shows that all the failures are the same. Note I've trimmed
> > the directory paths:
> >
> > gfor
On Tue, Sep 02, 2008 at 05:57:07PM -0300, Tobias Grosser wrote:
> Hi Steve,
>
> On Tue, 2008-09-02 at 13:49 -0700, Steve Kargl wrote:
> > x86_64-*-freebsd8.0
> >
> > FAIL: gfortran.dg/graphite/block-1.f90 -O (test for excess errors)
> > FAIL: gfortran.dg/
1 - 100 of 231 matches
Mail list logo
