https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329
--- Comment #8 from Janne Blomqvist ---
(In reply to Janne Blomqvist from comment #3)
> 1) When compiling an external procedure, for character(len=1) arguments we
> don't generate the hidden string length argument. And similarly when calling
> an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329
--- Comment #12 from Janne Blomqvist ---
(In reply to Tomas Kalibera from comment #11)
> At least in the case I debugged, I think gfortran could do better by not
> writing the 1 as string length to the place on the stack where the compiler
> know
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329
--- Comment #18 from Janne Blomqvist ---
(In reply to Thomas Koenig from comment #15)
> Since we applied the fix for PR 87689 to gcc 7, gcc 8 and gcc 9,
> I would suggest that we make -fno-optimize-sibling-calls
> the default on these branches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329
--- Comment #21 from Janne Blomqvist ---
I filed https://github.com/Reference-LAPACK/lapack/issues/339 to start a
discussion about fixing CBLAS and LAPACKE in upstream LAPACK.
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
Fortran 2018 removes the restriction that a file can be opened only on one unit
at a time.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90461
--- Comment #2 from Janne Blomqvist ---
Author: jb
Date: Wed May 15 18:02:36 2019
New Revision: 271260
URL: https://gcc.gnu.org/viewcvs?rev=271260&root=gcc&view=rev
Log:
Allow opening file on multiple units
As of Fortran 2018 it's allowed to op
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90461
Janne Blomqvist changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
Hanson, Hopkins, Remark on Algorithm 539: A Modern Fortran Reference
Implementation for Carefully Computing the Euclidean Norm,
https://dl.acm.org/citation.cfm?id=3134441
Above article tests
-
||patches/2019-05/msg00992.ht
||ml
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
--- Comment #1 from Janne Blomqvist ---
Patch at https://gcc.gnu.org/ml/gcc-patches/2019-05/msg00992
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #2 from Janne Blomqvist ---
Author: jb
Date: Fri May 17 18:18:04 2019
New Revision: 271340
URL: https://gcc.gnu.org/viewcvs?rev=271340&root=gcc&view=rev
Log:
libfortran/90038: Use posix_spawn instead of fork
fork() semantics can be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #3 from Janne Blomqvist ---
Further testing revealed that it leaves zombie processes around as the child is
never wait()'ed for. E.g.
program cmd
implicit none
call execute_command_line("echo hi", wait=.FALSE.)
call sleep(30)
e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #5 from Janne Blomqvist ---
(In reply to kargl from comment #4)
> What does 'it' refer to? fork() is leaving a zombie?
> posix_spawn() is leaving a zombie?
posix_spawn. Though I guess the old fork() code suffers from the same issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #7 from Janne Blomqvist ---
This should fix it:
--- a/libgfortran/intrinsics/execute_command_line.c
+++ b/libgfortran/intrinsics/execute_command_line.c
@@ -34,6 +34,7 @@ see the files COPYING3 and COPYING.RUNTIME respectively. If
no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #8 from Janne Blomqvist ---
Actually, wasn't this simple as the above patch broke the synchronous version.
Need to think more what to do.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #9 from Janne Blomqvist ---
Author: jb
Date: Sun May 19 19:38:11 2019
New Revision: 271384
URL: https://gcc.gnu.org/viewcvs?rev=271384&root=gcc&view=rev
Log:
libfortran/90038 Reap dead children when wait=.false.
When using posix_spa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
Janne Blomqvist changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #11 from Janne Blomqvist ---
Author: jb
Date: Mon May 20 17:43:05 2019
New Revision: 271427
URL: https://gcc.gnu.org/viewcvs?rev=271427&root=gcc&view=rev
Log:
libfortran/90038 Use posix_spawn, reap dead children when wait=.false.
Ba
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #12 from Janne Blomqvist ---
Author: jb
Date: Tue May 21 15:17:44 2019
New Revision: 271468
URL: https://gcc.gnu.org/viewcvs?rev=271468&root=gcc&view=rev
Log:
libfortran/90038: Document new wait=.false. implementation
2019-05-21 Ja
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90038
--- Comment #13 from Janne Blomqvist ---
Author: jb
Date: Tue May 21 15:24:30 2019
New Revision: 271470
URL: https://gcc.gnu.org/viewcvs?rev=271470&root=gcc&view=rev
Log:
libfortran/90038: Document new wait=.false. implementation
2019-05-21 Ja
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89100
--- Comment #12 from Janne Blomqvist ---
Author: jb
Date: Wed May 22 11:56:01 2019
New Revision: 271511
URL: https://gcc.gnu.org/viewcvs?rev=271511&root=gcc&view=rev
Log:
fortran/89100: Default widths with -fdec-format-defaults
gcc/fortran Chan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65921
--- Comment #2 from Janne Blomqvist ---
libgfortran/runtime/memory.c (xmallocarray) has been fixed for GCC 10, frontend
part still todo.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65921
--- Comment #3 from Janne Blomqvist ---
Author: jb
Date: Thu Jun 20 20:26:39 2019
New Revision: 272520
URL: https://gcc.gnu.org/viewcvs?rev=272520&root=gcc&view=rev
Log:
libfortran/65921: Add forgotten PR number to ChangeLog
2019-06-14 Janne B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91048
--- Comment #1 from Janne Blomqvist ---
Author: jb
Date: Tue Jul 2 05:54:31 2019
New Revision: 272921
URL: https://gcc.gnu.org/viewcvs?rev=272921&root=gcc&view=rev
Log:
mklog/91048: Open ~/.mklog in string mode.
2019-07-02 Janne Blomqvist
|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
--- Comment #2 from Janne Blomqvist ---
Thanks for the report. Fixed, closing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329
--- Comment #50 from Janne Blomqvist ---
Jakub, should your fix be backported to the gcc-7 branch as well, considering
that the PR 87689 fix was applied to that branch as well?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #36
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030
--- Comment #37 from Janne Blomqvist ---
One thing we could do would be to switch to pread and pwrite instead of using
lseek. That would avoid a few syscalls when updating the record length marker.
Though I guess the issue with GPFS isn't directl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030
--- Comment #38 from Janne Blomqvist ---
First, I think there's a bug in the benchmark in comment #c20. It writes
blocksize * sizeof(double), but then advances only blocksize for each iteration
of the loop. Fixed version writing just bytes below:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030
--- Comment #39 from Janne Blomqvist ---
Now, with the fixed benchmark in the previous comment, on Lustre (version 2.5)
system I get:
Test using 25000 bytes
Block size of file system: 4096
bs = 1024, 53.27 MiB/s
bs = 2048, 73.99
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
Currently the GCC website is "XHTML 1.0 Transitional". This specification has
been superseded in favor of the latest HTML version, currently 5.2 (see
https://www.w3.org/TR/xhtml1/ ).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87050
--- Comment #2 from Janne Blomqvist ---
The validation script that runs upon committing a change and sends email likely
needs to change too. There is https://validator.github.io/validator/ that can
be run as a batch script (needs java), or one c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87064
--- Comment #2 from Janne Blomqvist ---
I'm a bit confused, r263751 should only affect behavior wrt NaN's and possibly
signed zeroes, and AFAICS none of those are present in the testcase. Can you
print out the values of rv and vresult just before
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87050
--- Comment #4 from Janne Blomqvist ---
Sure, I can chip in a little, though I'm no html expert. Do you have some
branch somewhere where you're working, or?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87064
--- Comment #4 from Janne Blomqvist ---
Well, that is, ahem, interesting. So it seems that OACC does the vector_length
reduction incorrectly; the correct result is obviously 10.0 and not 9.0 which
then causes the failure.
I'm a bit lost why that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87064
Janne Blomqvist changed:
What|Removed |Added
CC||cesar at codesourcery dot com
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87050
--- Comment #5 from Janne Blomqvist ---
I looked through some mails in the archives, and I learned that the current
wwwdocs uses metahtml, which hasn't been maintained for years and years, and
doesn't even compile anymore. Ugh!
For an even more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87050
--- Comment #7 from Janne Blomqvist ---
(In reply to jos...@codesourcery.com from comment #6)
> A replacement for MetaHTML is already available, we just need to switch to
> using it.
>
> https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00176.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87050
--- Comment #11 from Janne Blomqvist ---
(In reply to Gerald Pfeifer from comment #10)
> (In reply to Janne Blomqvist from comment #0)
> > So apart from the headers, little work ought to be needed for the
> > conversion itself.
>
> Well, no. :-}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53796
--- Comment #22 from Janne Blomqvist ---
Author: jb
Date: Fri Sep 7 18:59:50 2018
New Revision: 264163
URL: https://gcc.gnu.org/viewcvs?rev=264163&root=gcc&view=rev
Log:
Remove unused init_unsigned_integer function.
As pointed out by Bernhard
: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
The recent patch to clobber intent(out) variables before a call appears to
cause a regression in one of the OpenCoarrays
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87337
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86119
--- Comment #4 from Janne Blomqvist ---
(In reply to janus from comment #3)
> (In reply to Dominique d'Humieres from comment #1)
> > Likely revision r256284.
>
> Certainly.
>
> For the code in comment 0, -fdump-tree-original shows:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84487
--- Comment #3 from Janne Blomqvist ---
I suspect it's working as intended. From the patch there is this comment which
explains in equivalent C code the code which is generated:
/* The string copy algorithm below generates code like
- if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84509
Janne Blomqvist changed:
What|Removed |Added
Component|gcov-profile|fortran
--- Comment #1 from Janne Blom
: normal
Priority: P3
Component: gcov-profile
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Consider the program
! compile with -fdefault-integer-8
program test
stop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
--- Comment #28 from Janne Blomqvist ---
Author: jb
Date: Thu Feb 22 16:14:21 2018
New Revision: 257903
URL: https://gcc.gnu.org/viewcvs?rev=257903&root=gcc&view=rev
Log:
PR 78534, 84509 Fix libgfortran API for PAUSE statement
This patch change
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84509
--- Comment #2 from Janne Blomqvist ---
Author: jb
Date: Thu Feb 22 16:14:21 2018
New Revision: 257903
URL: https://gcc.gnu.org/viewcvs?rev=257903&root=gcc&view=rev
Log:
PR 78534, 84509 Fix libgfortran API for PAUSE statement
This patch changes
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
In F2018 the STOP and ERROR STOP statements take and extra QUIET= specifier, a
logical value determining whether any information should be printed to the
screen or not.
For
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84519
Janne Blomqvist changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84519
--- Comment #2 from Janne Blomqvist ---
Author: jb
Date: Fri Feb 23 09:07:24 2018
New Revision: 257928
URL: https://gcc.gnu.org/viewcvs?rev=257928&root=gcc&view=rev
Log:
PR 84519 Handle optional QUIET specifier for STOP and ERROR STOP
Fortran 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84519
Janne Blomqvist changed:
What|Removed |Added
Assignee|jb at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84509
Janne Blomqvist changed:
What|Removed |Added
Summary|STOP and PAUSE statements |STOP and ERROR STOP
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
Bug 78534 depends on bug 83344, which changed state.
Bug 83344 Summary: Use of uninitialized memory with ASSOCIATE and strings
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83344
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83344
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83975
Janne Blomqvist changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84619
--- Comment #2 from Janne Blomqvist ---
size_t is the documented type, but for various reasons due to idiosyncrasies in
the gfortran frontend, for the moment it emits a signed type the same size as
size_t.
Just use size_t, that should work fine
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34742
Janne Blomqvist changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615
--- Comment #9 from Janne Blomqvist ---
(In reply to Dominique d'Humieres from comment #8)
> Another test that does not require -fdefault-integer-8
>
> module chtest
> contains
> function chararray2string(chararray) result(text)
> characte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615
--- Comment #11 from Janne Blomqvist ---
Yes, makes sense. And the same happens if one uses an external function with a
hand-rolled interface declaration:
function chararray2string(chararray) result(text)
character(len=1), dimension(:) :: char
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615
--- Comment #12 from Janne Blomqvist ---
So to be clear, the problem seems to be that while the code generation for the
function itself appears Ok, it generates the interface wrong (i.e. uses the
declared charlen kind instead of C_SIZE_T), and th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615
--- Comment #14 from Janne Blomqvist ---
(In reply to Thomas Koenig from comment #13)
> (In reply to Janne Blomqvist from comment #12)
> > So to be clear, the problem seems to be that while the code generation for
> > the function itself appears
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615
--- Comment #16 from Janne Blomqvist ---
The following patch regtests cleanly on x86_64-pc-linux-gnu, i686-pc-linux-gnu,
and successfully passes the #c5 testcase on i686 with -fdefault-real8, and the
#c8 testcase on i686 (I didn't test other test
-
||patches/2018-03/msg01057.ht
||ml
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
--- Comment #19 from Janne Blomqvist ---
Patch here: https://gcc.gnu.org/ml/gcc-patches/2018-03
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615
--- Comment #20 from Janne Blomqvist ---
Author: jb
Date: Wed Mar 21 18:46:44 2018
New Revision: 258736
URL: https://gcc.gnu.org/viewcvs?rev=258736&root=gcc&view=rev
Log:
PR 84615 Regressions due to type mismatch with character functions
Since
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32770
Bug 32770 depends on bug 84615, which changed state.
Bug 84615 Summary: [8 Regression] Executable Segfault for some tests compiled
with -m32 after r256284
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77941
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77941
--- Comment #8 from Janne Blomqvist ---
(In reply to Steve Kargl from comment #7)
> On Thu, Mar 22, 2018 at 07:53:14AM +0000, jb at gcc dot gnu.org wrote:
> >
> > It works on x86_64-pc-linux-gnu (including running it), but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77941
--- Comment #9 from Janne Blomqvist ---
(In reply to Steve Kargl from comment #7)
> I suppose one could always check that a length type parameter
> less than some max integer based on 32-bit vs 64-bit system,
> but that would pessimize all uses
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87352
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87050
--- Comment #12 from Janne Blomqvist ---
Based on a recursive grep of the wwwdocs repo the only remaining use of "xhtml"
is a variable "XHTML" in htdocs/style.mhtml which, AFAICS, doesn't any longer
actually have anything to do with XHTML.
A big
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87050
Janne Blomqvist changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
Following the recent upgrade to autoconf 2.69 and automake 1.15.1, we should
switch libgfortran to use the "subdir-objects" option for automake. However,
the patch
di
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87851
--- Comment #5 from Janne Blomqvist ---
(In reply to Dominique d'Humieres from comment #4)
> > Yes, but the return type on the library side changed.
>
> When and how do you see that?
As part of my patch to change the string length type, in the
||2018-11-22
CC||jb at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Janne Blomqvist ---
Confirmed. This also occurs on x86_64-pc-linux-gnu with the latest trunk (9.0.0
20181122). Apparently
||2018-11-22
CC||jb at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Janne Blomqvist ---
Confirmed on latest trunk (9.0.0 20181122), x86_64-pc-linux-gnu
Changing the example to execute 10 iterations
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88137
Janne Blomqvist changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88137
Janne Blomqvist changed:
What|Removed |Added
URL||https://gcc.gnu.org/ml/gcc-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88137
--- Comment #4 from Janne Blomqvist ---
Author: jb
Date: Fri Nov 30 16:44:27 2018
New Revision: 266677
URL: https://gcc.gnu.org/viewcvs?rev=266677&root=gcc&view=rev
Log:
Initialize backtrace state once
From backtrace.h for backtrace_create_stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88137
--- Comment #5 from Janne Blomqvist ---
Author: jb
Date: Fri Nov 30 16:46:55 2018
New Revision: 266678
URL: https://gcc.gnu.org/viewcvs?rev=266678&root=gcc&view=rev
Log:
Initialize backtrace state once
From backtrace.h for backtrace_create_stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88137
--- Comment #6 from Janne Blomqvist ---
Author: jb
Date: Sun Dec 2 15:12:44 2018
New Revision: 266724
URL: https://gcc.gnu.org/viewcvs?rev=266724&root=gcc&view=rev
Log:
Use atomic load/store to access static backtrace state pointer
As the stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88137
--- Comment #7 from Janne Blomqvist ---
Author: jb
Date: Sun Dec 2 15:14:51 2018
New Revision: 266725
URL: https://gcc.gnu.org/viewcvs?rev=266725&root=gcc&view=rev
Log:
Use atomic load/store to access static backtrace state pointer
As the stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88137
--- Comment #8 from Janne Blomqvist ---
Author: jb
Date: Thu Dec 6 15:38:25 2018
New Revision: 266858
URL: https://gcc.gnu.org/viewcvs?rev=266858&root=gcc&view=rev
Log:
Initialize backtrace state once
From backtrace.h for backtrace_create_stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88137
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30162
--- Comment #29 from Janne Blomqvist 2012-11-25
15:08:24 UTC ---
(In reply to comment #28)
> (In reply to comment #27)
> > (In reply to comment #26)
> > > Is this caused by
> > >
> > > http://gcc.gnu.org/viewcvs?view=revision&revision=
||2012-11-25
AssignedTo|unassigned at gcc dot |jb at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
--- Comment #4 from Janne Blomqvist 2012-11-25 15:10:07
UTC ---
I have a patch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
Janne Blomqvist changed:
What|Removed |Added
CC||ian at airs dot com
--- Comme
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #6 from Janne Blomqvist 2012-11-26 16:46:08
UTC ---
Created attachment 28779
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28779
Patch to use libbacktrace
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55473
Bug #: 55473
Summary: quadmath.h should have extern "C" for C++ users
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhance
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #9 from Janne Blomqvist 2012-11-27 08:58:59
UTC ---
(In reply to comment #7)
> Why are there no line numbers in the backtrace from gdb? You said you
> compiled
> with -g. Are you sure that libbacktrace itself was compiled wi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #12 from Janne Blomqvist 2012-11-30
21:56:29 UTC ---
(In reply to comment #9)
> (In reply to comment #7)
> > Why are there no line numbers in the backtrace from gdb? You said you
> > compiled
> > with -g. Are you sure that
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #13 from Janne Blomqvist 2012-11-30
22:03:43 UTC ---
(In reply to comment #10)
> (In reply to comment #6)
> > Created attachment 28779 [details]
> > Patch to use libbacktrace
>
> I have to apply the following patch on your
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #15 from Janne Blomqvist 2012-12-01
19:48:12 UTC ---
(In reply to comment #14)
> Thanks for the additional info.
>
> #1 0x77bb53be in build_address_map (addrs=0x7fffc710,
> data=0x7fffcf1c,
> error_cal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594
--- Comment #7 from Janne Blomqvist 2012-12-14 08:44:44
UTC ---
(In reply to comment #6)
> I was just about to file a bugreport that STOP 1 should yield a backtrace if
> compiled with -fbacktrace that would really be useful to debug co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55539
Janne Blomqvist changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot |jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55539
--- Comment #6 from Janne Blomqvist 2012-12-15 16:47:44
UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > Strangely enough I needed to add some epsilon to 0.5 so that
> > the second test passes, because the exact value 0.5 appears
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55539
--- Comment #7 from Janne Blomqvist 2012-12-25 22:11:21
UTC ---
Author: jb
Date: Tue Dec 25 22:11:16 2012
New Revision: 194717
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194717
Log:
PR fortran/55539 Fix regression in -fno-s
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55539
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25071
--- Comment #18 from Janne Blomqvist ---
(In reply to janus from comment #16)
> Any opinions on this?
+1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46686
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
301 - 400 of 690 matches
Mail list logo
