[Bug c++/61538] g++ compiled binary, linked to glibc libpthread, hangs on SGI MIPS R1x000 systems on Linux

2014-07-21 Thread kumba at gentoo dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61538 --- Comment #17 from Joshua Kinard kumba at gentoo dot org --- (In reply to Joshua Kinard from comment #16) In 'all-stage2-gcc'. That's right around the commit you're referencing, so I went ahead and reversed these four commits: 1.

[Bug regression/61538] gcc after commit 39a8c5ea produces bad code for MIPS R1x000 CPUs

2014-07-21 Thread kumba at gentoo dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61538 Joshua Kinard kumba at gentoo dot org changed: What|Removed |Added Component|c++ |regression

[Bug fortran/61831] [4.9/ 4.10 Regression] runtime error: pointer being freed was not allocated

2014-07-21 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61831 Dominique d'Humieres dominiq at lps dot ens.fr changed: What|Removed |Added CC||mikael

[Bug target/61855] _MM_MANTISSA_NORM_ENUM in avx512intrin.h disabled when optimization off

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61855 Uroš Bizjak ubizjak at gmail dot com changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last

[Bug target/61855] _MM_MANTISSA_NORM_ENUM in avx512intrin.h disabled when optimization off

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61855 Uroš Bizjak ubizjak at gmail dot com changed: What|Removed |Added Target||x86 Target

[Bug regression/61538] gcc after commit 39a8c5ea produces bad code for MIPS R1x000 CPUs

2014-07-21 Thread kumba at gentoo dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61538 --- Comment #19 from Joshua Kinard kumba at gentoo dot org --- Created attachment 33165 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33165action=edit Disassembly of the ASM from 'sln' compiled by a known working gcc-4.8.0. This is the

[Bug regression/61538] gcc after commit 39a8c5ea produces bad code for MIPS R1x000 CPUs

2014-07-21 Thread kumba at gentoo dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61538 --- Comment #20 from Joshua Kinard kumba at gentoo dot org --- Created attachment 33166 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33166action=edit Disassembly of the ASM from 'sln' compiled by a non-working gcc-4.8.0. This is the

[Bug target/61855] _MM_MANTISSA_NORM_ENUM in avx512intrin.h disabled when optimization off

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61855 --- Comment #2 from Uroš Bizjak ubizjak at gmail dot com --- Author: uros Date: Mon Jul 21 08:47:48 2014 New Revision: 212886 URL: https://gcc.gnu.org/viewcvs?rev=212886root=gccview=rev Log: PR target/61855 * config/i386/avx512fintrin.h:

[Bug target/61827] gcc.target/i386/fuse-caller-save-xmm.c FAILs

2014-07-21 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61827 --- Comment #2 from vries at gcc dot gnu.org --- Author: vries Date: Mon Jul 21 09:11:04 2014 New Revision: 212888 URL: https://gcc.gnu.org/viewcvs?rev=212888root=gccview=rev Log: Fix fuse-caller-save-xmm.c test-case 2014-07-21 Tom de Vries

[Bug target/61827] gcc.target/i386/fuse-caller-save-xmm.c FAILs

2014-07-21 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61827 vries at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug go/61865] New: FAIL: go.test/test/fixedbugs/bug272.go execution, -O2 -g

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61865 Bug ID: 61865 Summary: FAIL: go.test/test/fixedbugs/bug272.go execution, -O2 -g Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug go/61866] New: FAIL: ./index0-out.go execution, -O0 -g -fno-var-tracking-assignments

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61866 Bug ID: 61866 Summary: FAIL: ./index0-out.go execution, -O0 -g -fno-var-tracking-assignments Product: gcc Version: 4.10.0 Status: UNCONFIRMED Severity: normal

[Bug target/61827] gcc.target/i386/fuse-caller-save-xmm.c FAILs

2014-07-21 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61827 --- Comment #4 from Dominique d'Humieres dominiq at lps dot ens.fr --- The following patch --- ../_clean/gcc/testsuite/gcc.target/i386/fuse-caller-save-xmm.c 2014-07-21 11:21:30.0 +0200 +++

[Bug target/61855] _MM_MANTISSA_NORM_ENUM in avx512intrin.h disabled when optimization off

2014-07-21 Thread uros at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61855 --- Comment #3 from uros at gcc dot gnu.org --- Author: uros Date: Mon Jul 21 10:09:04 2014 New Revision: 212889 URL: https://gcc.gnu.org/viewcvs?rev=212889root=gccview=rev Log: Backport from mainline 2014-07-21 Uros Bizjak

[Bug target/61855] _MM_MANTISSA_NORM_ENUM in avx512intrin.h disabled when optimization off

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61855 Uroš Bizjak ubizjak at gmail dot com changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug c++/61863] Data corruption when creating temporary object

2014-07-21 Thread mikpelinux at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61863 Mikael Pettersson mikpelinux at gmail dot com changed: What|Removed |Added CC|

[Bug target/61827] gcc.target/i386/fuse-caller-save-xmm.c FAILs

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61827 --- Comment #5 from Uroš Bizjak ubizjak at gmail dot com --- (In reply to Dominique d'Humieres from comment #4) The following patch --- ../_clean/gcc/testsuite/gcc.target/i386/fuse-caller-save-xmm.c 2014-07-21 11:21:30.0 +0200 +++

[Bug c++/61867] New: gcc can't detect obviously false test

2014-07-21 Thread dcb314 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61867 Bug ID: 61867 Summary: gcc can't detect obviously false test Product: gcc Version: 4.9.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug fortran/61831] [4.9/ 4.10 Regression] runtime error: pointer being freed was not allocated

2014-07-21 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61831 --- Comment #31 from Dominique d'Humieres dominiq at lps dot ens.fr --- Further reduced test program main implicit none type :: string_t character(LEN=1), dimension(:), allocatable :: chars end type string_t type(string_t) ::

[Bug target/61827] gcc.target/i386/fuse-caller-save-xmm.c FAILs

2014-07-21 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61827 --- Comment #6 from vries at gcc dot gnu.org --- Author: vries Date: Mon Jul 21 10:54:47 2014 New Revision: 212890 URL: https://gcc.gnu.org/viewcvs?rev=212890root=gccview=rev Log: Fix fuse-caller-save test-cases 2014-07-21 Tom de Vries

[Bug target/61827] gcc.target/i386/fuse-caller-save-xmm.c FAILs

2014-07-21 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61827 --- Comment #7 from Dominique d'Humieres dominiq at lps dot ens.fr --- Sorry, another patch for darwin (call_bar) --- ../_clean/gcc/testsuite/gcc.target/i386/fuse-caller-save-rec.c 2014-07-21 13:09:41.0 +0200 +++

[Bug target/61827] gcc.target/i386/fuse-caller-save-xmm.c FAILs

2014-07-21 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61827 --- Comment #8 from vries at gcc dot gnu.org --- Author: vries Date: Mon Jul 21 11:29:10 2014 New Revision: 212891 URL: https://gcc.gnu.org/viewcvs?rev=212891root=gccview=rev Log: Fix fuse-caller-save-rec.c 2014-07-21 Tom de Vries

[Bug target/61827] gcc.target/i386/fuse-caller-save-xmm.c FAILs

2014-07-21 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61827 --- Comment #9 from Dominique d'Humieres dominiq at lps dot ens.fr --- New Revision: 212891 ... Thanks!

[Bug target/55701] Inline some instances of memset for ARM

2014-07-21 Thread amker at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55701 --- Comment #3 from amker at gcc dot gnu.org --- Author: amker Date: Mon Jul 21 12:24:06 2014 New Revision: 212893 URL: https://gcc.gnu.org/viewcvs?rev=212893root=gccview=rev Log: PR target/55701 * config/arm/arm.md (setmem): New

[Bug go/60874] FAIL: go.test/test/recover.go execution

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60874 Uroš Bizjak ubizjak at gmail dot com changed: What|Removed |Added Status|WAITING |NEW --- Comment

[Bug c++/61867] gcc can't detect obviously false test

2014-07-21 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61867 --- Comment #1 from Jonathan Wakely redi at gcc dot gnu.org --- I'm pretty sure gcc does detect it and optimizes appropriately, it just doesn't warn (because it's not a static analyzer)

[Bug driver/61868] New: -frandom-seed always results in random_seed of 0

2014-07-21 Thread bmei at broadcom dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61868 Bug ID: 61868 Summary: -frandom-seed always results in random_seed of 0 Product: gcc Version: 4.10.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/61869] New: Spurious uninitialized warning

2014-07-21 Thread y.gribov at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61869 Bug ID: 61869 Summary: Spurious uninitialized warning Product: gcc Version: 4.10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c++/61870] New: internal compiler error: in get_expr_operands, at tree-ssa-operands.c:1035

2014-07-21 Thread dzidzitop at vfemail dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61870 Bug ID: 61870 Summary: internal compiler error: in get_expr_operands, at tree-ssa-operands.c:1035 Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity:

[Bug c++/61870] internal compiler error: in get_expr_operands, at tree-ssa-operands.c:1035

2014-07-21 Thread dzidzitop at vfemail dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61870 --- Comment #1 from dzidzitop at vfemail dot net --- Created attachment 33168 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33168action=edit The preprocessed file.

[Bug go/60874] FAIL: go.test/test/recover.go execution

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60874 --- Comment #4 from Uroš Bizjak ubizjak at gmail dot com --- (In reply to Uroš Bizjak from comment #3) (In reply to Ian Lance Taylor from comment #2) The patch is committed so this bug may be fixed. I haven't tested it on Alpha, though.

[Bug go/60874] FAIL: go.test/test/recover.go execution

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60874 --- Comment #5 from Uroš Bizjak ubizjak at gmail dot com --- I forgot to tell that reflect test from libgo testsuite now passes: PASS: reflect

[Bug go/61871] New: FAIL: regexp from libgo testsuite on non-split stack targets

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871 Bug ID: 61871 Summary: FAIL: regexp from libgo testsuite on non-split stack targets Product: gcc Version: 4.10.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/61847] bug in gfortran runtime on OSX: digits cut off when reading floating point number

2014-07-21 Thread e2cd58e1 at opayq dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #3 from e2cd58e1 at opayq dot com --- but what I want to do is read in values with point as decimal separator. Using open(unit=1,file='bug.dat', decimal=point) doesn't seem to change anything.

[Bug lto/61526] relocation R_X86_64_PC32 in shared object with static and extern

2014-07-21 Thread sandra at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61526 Sandra Loosemore sandra at codesourcery dot com changed: What|Removed |Added CC||sandra

[Bug lto/61526] relocation R_X86_64_PC32 in shared object with static and extern

2014-07-21 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61526 --- Comment #4 from Uroš Bizjak ubizjak at gmail dot com --- (In reply to Sandra Loosemore from comment #3) The testcase added for this bug in GCC 4.9.1 is failing with a link error on an arm-none-eabi target that doesn't support -shared.

[Bug c++/61872] New: Assigning to long double causes memset to be improperly elided

2014-07-21 Thread coleb at eyesopen dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61872 Bug ID: 61872 Summary: Assigning to long double causes memset to be improperly elided Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal

[Bug c++/61873] New: with -openmp, -E does not produce preprocessed output on stdout

2014-07-21 Thread mib.bugzilla at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61873 Bug ID: 61873 Summary: with -openmp, -E does not produce preprocessed output on stdout Product: gcc Version: 4.8.3 Status: UNCONFIRMED Severity: normal

[Bug fortran/61847] bug in gfortran runtime on OSX: digits cut off when reading floating point number

2014-07-21 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug fortran/61847] bug in gfortran runtime on OSX: digits cut off when reading floating point number

2014-07-21 Thread e2cd58e1 at opayq dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #5 from e2cd58e1 at opayq dot com --- I actually don't know - how can I test this? But either way, shouldn't open(unit=1,file='bug.dat', decimal=point) read 1.234 in as 1.234 no matter what the locale settings are?

[Bug fortran/61847] bug in gfortran runtime on OSX: digits cut off when reading floating point number

2014-07-21 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #6 from kargl at gcc dot gnu.org --- (In reply to kargl from comment #4) (In reply to e2cd58e1 from comment #3) but what I want to do is read in values with point as decimal separator. Using open(unit=1,file='bug.dat',

[Bug fortran/61847] bug in gfortran runtime on OSX: digits cut off when reading floating point number

2014-07-21 Thread e2cd58e1 at opayq dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #7 from e2cd58e1 at opayq dot com --- For printf(Test 1 = %.4f\n,strtod(1.2345,NULL)); printf(Test 2 = %.4f\n,strtod(1,2345,NULL)); I get Test 1 = 1, Test 2 = 1,2345

[Bug fortran/61847] bug in gfortran runtime on OSX: digits cut off when reading floating point number

2014-07-21 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #8 from Steve Kargl sgk at troutmask dot apl.washington.edu --- On Mon, Jul 21, 2014 at 06:18:14PM +, e2cd58e1 at opayq dot com wrote: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #7 from e2cd58e1 at opayq

[Bug fortran/61847] bug in gfortran runtime on OSX: digits cut off when reading floating point number

2014-07-21 Thread e2cd58e1 at opayq dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #9 from e2cd58e1 at opayq dot com --- Just what I get: 1.2345 = 1.2345 and 5,4321 = 5. 1.2345 = 1, and 5,4321 = 5,4321

[Bug tree-optimization/61869] Spurious uninitialized warning

2014-07-21 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61869 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last

[Bug middle-end/61396] [4.10 regression] ICE in simplify_immed_subreg

2014-07-21 Thread pthaugen at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61396 --- Comment #4 from Pat Haugen pthaugen at gcc dot gnu.org --- (In reply to Iain Sandoe from comment #3) Revision r209530 is OK, r210534 is not, likely a wide-int fallout. The problem first appeared in trunk revision 210113.

[Bug c++/61867] gcc can't detect obviously false test

2014-07-21 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61867 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC||manu at gcc

[Bug fortran/61831] [4.9/ 4.10 Regression] runtime error: pointer being freed was not allocated

2014-07-21 Thread paul.richard.thomas at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61831 --- Comment #32 from paul.richard.thomas at gmail dot com paul.richard.thomas at gmail dot com --- Dear Dominique, The problem is due to: atmp.10.offset = 0; { integer(kind=8) S.12;

[Bug fortran/61847] bug in gfortran runtime: digits cut off when reading floating point number

2014-07-21 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 Dominique d'Humieres dominiq at lps dot ens.fr changed: What|Removed |Added Summary|bug in gfortran runtime on |bug in

[Bug c++/61867] gcc can't detect obviously false test

2014-07-21 Thread dcb314 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61867 --- Comment #3 from David Binderman dcb314 at hotmail dot com --- (In reply to Jonathan Wakely from comment #1) I'm pretty sure gcc does detect it and optimizes appropriately, it just doesn't warn. I've checked the output from using -S and I

[Bug fortran/61831] [4.9/ 4.10 Regression] runtime error: pointer being freed was not allocated

2014-07-21 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61831 --- Comment #33 from Dominique d'Humieres dominiq at lps dot ens.fr --- Dear Paul, I cannot see yet, where it comes in nor when it was introduced. Unfortunately I has been introduced by me, see comment 5. The code is + if (expr-ts.type ==

[Bug target/61407] Build errors on latest OS X 10.10 Yosemite with Xcode 6 on GCC 4.8.3

2014-07-21 Thread jrtc27 at jrtc27 dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407 James Clarke jrtc27 at jrtc27 dot com changed: What|Removed |Added CC||jrtc27 at jrtc27

[Bug target/61407] Build errors on latest OS X 10.10 Yosemite with Xcode 6 on GCC 4.8.3

2014-07-21 Thread jrtc27 at jrtc27 dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407 --- Comment #15 from James Clarke jrtc27 at jrtc27 dot com --- (In reply to James Clarke from comment #14) The issue with Availability.h has been fixed as of Developer Preview 4, however `all-stage1-target-libsanitizer` still fails with Error

[Bug fortran/61847] bug in gfortran runtime: digits cut off when reading floating point number

2014-07-21 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #11 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- After all that has been said here, I am almost afraid to add any more. This is not a bug. Fortran and GFortran are not locale aware. The ',' or '.' are read from the file or

[Bug fortran/61847] bug in gfortran runtime: digits cut off when reading floating point number

2014-07-21 Thread e2cd58e1 at opayq dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #12 from e2cd58e1 at opayq dot com --- Sorry but I still have a problem with this, maybe I didn't get what you are saying or I wasn't clear enough. Suppose I cannot change the C-wrapper and the locale might be set to whatever. The

[Bug debug/61874] New: Missing DW_AT_location for this parameter when using always_inline attribute

2014-07-21 Thread apepper at blueshiftinc dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61874 Bug ID: 61874 Summary: Missing DW_AT_location for this parameter when using always_inline attribute Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity:

[Bug fortran/61847] bug in gfortran runtime: digits cut off when reading floating point number

2014-07-21 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #13 from Steve Kargl sgk at troutmask dot apl.washington.edu --- On Tue, Jul 22, 2014 at 01:39:30AM +, jvdelisle at gcc dot gnu.org wrote: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #11 from Jerry DeLisle

[Bug c++/53361] Could not convert ‘{0, 0, 0}’ from ‘brace-enclosed initializer list’ to ‘std::arrayunsigned int, 3ul’

2014-07-21 Thread nightstrike at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53361 nightstrike nightstrike at gmail dot com changed: What|Removed |Added CC||nightstrike at

[Bug fortran/61847] bug in gfortran runtime: digits cut off when reading floating point number

2014-07-21 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #14 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- (In reply to e2cd58e1 from comment #12) --- snip --- Suppose I cannot change the C-wrapper and the locale might be set to whatever. The file bug.dat already exists and uses

[Bug fortran/61847] bug in gfortran runtime: digits cut off when reading floating point number

2014-07-21 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #15 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Maybe something like this: Index: open.c === --- open.c(revision 212498) +++ open.c(working copy) @@

[Bug target/61396] [4.10 regression] ICE in simplify_immed_subreg

2014-07-21 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61396 Segher Boessenkool segher at gcc dot gnu.org changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug fortran/61847] bug in gfortran runtime: digits cut off when reading floating point number

2014-07-21 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #16 from Steve Kargl sgk at troutmask dot apl.washington.edu --- On Tue, Jul 22, 2014 at 04:27:58AM +, jvdelisle at gcc dot gnu.org wrote: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847 --- Comment #15 from Jerry DeLisle

[Bug c++/53361] Could not convert ‘{0, 0, 0}’ from ‘brace-enclosed initializer list’ to ‘std::arrayunsigned int, 3ul’

2014-07-21 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53361 --- Comment #9 from Andrew Pinski pinskia at gcc dot gnu.org --- (In reply to nightstrike from comment #8) This SO post claims that GCC is in error: Yes and it was fixed in 4.8.

[Bug c++/53361] Could not convert ‘{0, 0, 0}’ from ‘brace-enclosed initializer list’ to ‘std::arrayunsigned int, 3ul’

2014-07-21 Thread nightstrike at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53361 --- Comment #10 from nightstrike nightstrike at gmail dot com --- Oh, strange. I thought I was still experiencing this on 4.8.2. I'll check again. Sorry for the noise.