[Bug other/60099] internal compiler error: Segmentation fault

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60099 --- Comment #4 from David Kredba nheghathivhistha at gmail dot com --- Created attachment 32068 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32068action=edit testcase.i produced by c-reduce

[Bug other/60099] internal compiler error: Segmentation fault

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60099 --- Comment #5 from David Kredba nheghathivhistha at gmail dot com --- Created attachment 32069 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32069action=edit Original ii file gzipped

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 Jouko Orava jouko.orava at iki dot fi changed: What|Removed |Added CC||jouko.orava at iki

[Bug target/58785] [ARM] LRA issue in Thumb mode with movhi

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58785 --- Comment #2 from Yvan Roux yvan.roux at linaro dot org --- Yes, I fixed it at r205581 but the PR reference in the ChangeLog disappeared between the submission and the commit :( Yvan

[Bug target/58785] [ARM] LRA issue in Thumb mode with movhi

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58785 Yvan Roux yvan.roux at linaro dot org changed: What|Removed |Added Status|WAITING |RESOLVED

[Bug other/60099] internal compiler error: Segmentation fault

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60099 --- Comment #6 from David Kredba nheghathivhistha at gmail dot com --- Revision 207565 is fine with it.

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #7 from Dominique d'Humieres dominiq at lps dot ens.fr --- Confirmed. The second test case still segfaults when run if compiled with -static in Linux 3.8.0 x86_64 kernel on Ubuntu 12.04.4 LTS, using gfortran 4.6.3 (Ubuntu/Linaro

[Bug c/60100] New: warning disappears when preprocessed source is compiled

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100 Bug ID: 60100 Summary: warning disappears when preprocessed source is compiled Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: normal

[Bug c/60100] warning disappears when preprocessed source is compiled

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100 --- Comment #1 from Andrew Pinski pinskia at gcc dot gnu.org --- Also, I'm not sure why there is a bogus warning about linking here (and not when compiling right from the source file, above). Because your command line did not actual compile

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #10 from Dominique d'Humieres dominiq at lps dot ens.fr --- This could be a duplicate of pr50201.

[Bug c/60100] warning disappears when preprocessed source is compiled

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100 --- Comment #2 from lavr at ncbi dot nlm.nih.gov --- Because your command line did not actual compile anything. Indeed. with .i I see the warning again. But I can't see any warning if the precompiled file is processed through distcc...

[Bug c/60100] warning disappears when preprocessed source is compiled

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100 --- Comment #3 from lavr at ncbi dot nlm.nih.gov --- Ok, sorry and let me start again. My original mockup case wasn't good enough. So attached is the real (preprocessed) code that fails to produce a warning (yet when compiled from the .c form,

[Bug c/60101] New: Long compile times when mixed complex floating point datatypes are used in lengthy expressions

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60101 Bug ID: 60101 Summary: Long compile times when mixed complex floating point datatypes are used in lengthy expressions Product: gcc Version: 4.8.2 Status: UNCONFIRMED

[Bug c/60100] warning disappears when preprocessed source is compiled

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100 --- Comment #4 from lavr at ncbi dot nlm.nih.gov --- Created attachment 32072 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32072action=edit Preprocessed C source that fails to produce a warning when compiled

[Bug target/46481] long double should default to 64bit even for aix6.1

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46481 David Edelsohn dje at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #8 from Jouko Orava jouko.orava at iki dot fi --- I confirm, still occurs with 4.7.3 and 4.8.1. For simplicity, I obtained the 4.7 and 4.8 versions from Ubuntu toolchain test builds' PPA, https://launchpad.net/~ubuntu-toolchain-r/.

[Bug c++/59632] ICE with erroneous loop condition after #pragma GCC ivdep

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59632 Volker Reichelt reichelt at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |RESOLVED

[Bug rtl-optimization/52714] [4.7/4.8/4.9 regression] ICE in fixup_reorder_chain, at cfglayout.c:880

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52714 Jeffrey A. Law law at redhat dot com changed: What|Removed |Added CC||law at redhat dot

[Bug middle-end/60102] New: powerpc fp-bit ices at dwf_regno

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60102 Bug ID: 60102 Summary: powerpc fp-bit ices at dwf_regno Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #11 from Jacob Abel thatcadguy at gmail dot com --- The culprit that -march=native activates on my Core i7 laptop is -mavx. Compiling with -mavx causes the segfault, without is fine. Unfortunately, that flag was not set on my other

[Bug rtl-optimization/52714] [4.7/4.8/4.9 regression] ICE in fixup_reorder_chain, at cfglayout.c:880

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52714 --- Comment #13 from Jeffrey A. Law law at redhat dot com --- BTW, compiling with -O2 rather than -O1 makes this problem go away. The problematical sequence (testing that the result of an alloca call is nonzero) is eliminated by the VRP

[Bug rtl-optimization/60030] [4.9 regression] ICE in simplify_subreg, at simplify-rtx.c:5903

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60030 --- Comment #2 from Jakub Jelinek jakub at gcc dot gnu.org --- Author: jakub Date: Thu Feb 6 21:54:21 2014 New Revision: 207582 URL: http://gcc.gnu.org/viewcvs?rev=207582root=gccview=rev Log: PR rtl-optimization/60030 * internal-fn.c

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #12 from Jacob Abel thatcadguy at gmail dot com --- Created attachment 32074 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32074action=edit NEW smaller simpler file to create the segfault

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #13 from Jacob Abel thatcadguy at gmail dot com --- The following file: SUBROUTINE test(N) IMPLICIT NONE INTEGER, INTENT(IN) :: N REAL(KIND=16) :: array(N) array = 0 END SUBROUTINE test PROGRAM main IMPLICIT NONE CALL test(10) END

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #14 from kargl at gcc dot gnu.org --- (In reply to Jacob Abel from comment #8) Seriously? Look, you falsely assumed it was mingw only. Yes, with the information I had at the time, I thought the problem was mingw specific. No wonder

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #9 from Jouko Orava jouko.orava at iki dot fi --- It turns out that while fdp2.f90, PROGRAM fdp2 IMPLICIT none INTEGER, PARAMETER :: b128 = SELECTED_REAL_KIND(33, 1000) REAL(KIND=b128) :: x(4) x =

[Bug driver/57951] -MG doesn't work with -MD

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57951 Douglas Bagnall douglas at halo dot gen.nz changed: What|Removed |Added CC||douglas at

[Bug target/60032] [4.9 regression] ICE in reload_cse_simplify_operands, at postreload.c:411

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60032 Alan Modra amodra at gmail dot com changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 Jouko Orava jouko.orava at iki dot fi changed: What|Removed |Added CC||jouko.orava at iki

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #16 from Jacob Abel thatcadguy at gmail dot com --- Still segfaults, at least on MinGW: C:\Users\Jake\Downloadsgfortran -march=native -Wl,-uquadmath_snprintf newtest.f 90 C:\Users\Jake\Downloadsa Program received signal SIGSEGV:

[Bug c/60103] New: Spurious -Wsequence-point warning with -O1

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60103 Bug ID: 60103 Summary: Spurious -Wsequence-point warning with -O1 Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c/60103] Spurious -Wsequence-point warning with -O1

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60103 --- Comment #1 from Andrew Pinski pinskia at gcc dot gnu.org --- I think C11 and C90/C99 have a different idea here. There is a relative sequence point between the function call fn2 and the 0 but there is no sequence point between the two

[Bug target/60104] New: load not folded into indirect branch on x86-64

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60104 Bug ID: 60104 Summary: load not folded into indirect branch on x86-64 Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: enhancement Priority: P3

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #18 from Jouko Orava jouko.orava at iki dot fi --- Addendum: the unaligned access causing the segfault seems to occur because __libc_malloc returns an address aligned to 8 bytes, but it is used as if it was aligned to 16 bytes. The

[Bug target/60077] [4.9 regression] gcc.target/i386/pr35767-5.c FAILs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60077 Jan Hubicka hubicka at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #19 from Jacob Abel thatcadguy at gmail dot com --- jake@Jake-E1505:~/Desktop$ gfortran -static -march=native -Wl,-uquadmath_snprintf newtest.f90 -o newtest jake@Jake-E1505:~/Desktop$ gdb newtest GNU gdb (GDB)

[Bug ipa/59918] [4.9 Regression] ICE in record_target_from_binfo, at ipa-devirt.c:693

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59918 Jan Hubicka hubicka at gcc dot gnu.org changed: What|Removed |Added Status|NEW |ASSIGNED ---

[Bug ipa/59469] [4.8/4.9 Regression] LLVM build failure with gcc LTO

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59469 --- Comment #47 from Jan Hubicka hubicka at gcc dot gnu.org --- Author: hubicka Date: Fri Feb 7 02:27:05 2014 New Revision: 207589 URL: http://gcc.gnu.org/viewcvs?rev=207589root=gccview=rev Log: PR ipa/59469 * lto-cgraph.c

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #17 from Jouko Orava jouko.orava at iki dot fi --- I asked and received the details from Jacob Abel off-list, to find out if this bug #60088 is related to bug #50201. They do not seem to be. The instruction causing the segfault in

[Bug ipa/59469] [4.8/4.9 Regression] LLVM build failure with gcc LTO

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59469 Jan Hubicka hubicka at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug target/60077] [4.9 regression] gcc.target/i386/pr35767-5.c FAILs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60077 --- Comment #4 from Jan Hubicka hubicka at gcc dot gnu.org --- Author: hubicka Date: Fri Feb 7 02:11:27 2014 New Revision: 207587 URL: http://gcc.gnu.org/viewcvs?rev=207587root=gccview=rev Log: PR target/60077 * expr.c

[Bug ipa/59469] [4.8/4.9 Regression] LLVM build failure with gcc LTO

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59469 --- Comment #49 from Jan Hubicka hubicka at gcc dot gnu.org --- Author: hubicka Date: Fri Feb 7 02:28:33 2014 New Revision: 207591 URL: http://gcc.gnu.org/viewcvs?rev=207591root=gccview=rev Log: PR ipa/59469 * lto-cgraph.c

[Bug ipa/59469] [4.8/4.9 Regression] LLVM build failure with gcc LTO

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59469 --- Comment #48 from Jan Hubicka hubicka at gcc dot gnu.org --- Author: hubicka Date: Fri Feb 7 02:27:37 2014 New Revision: 207590 URL: http://gcc.gnu.org/viewcvs?rev=207590root=gccview=rev Log: PR ipa/59469 * lto-cgraph.c

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #20 from Jouko Orava jouko.orava at iki dot fi --- Apologies, Jacob; my advice was faulty. Could you please retest using the following? Compile the binary using gfortran -march=native -ggdb newtest.f90 -o newtest then start gdb,

[Bug libgomp/60035] [PATCH] make it possible to use OMP on both sides of a fork (without violating standard)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60035 Conrad conradsand.arma at gmail dot com changed: What|Removed |Added CC||conradsand.arma

[Bug c++/19377] Using declaration in private part causes protected diagnostic

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19377 --- Comment #11 from Andrey Belevantsev abel at gcc dot gnu.org --- (In reply to fabien from comment #10) The testcase is not valid, as a using declaration shall refer to a direct base class, which is not the case in 'using ns::Base::i' (the

[Bug ipa/59918] [4.9 Regression] ICE in record_target_from_binfo, at ipa-devirt.c:693

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59918 --- Comment #8 from Jan Hubicka hubicka at gcc dot gnu.org --- This is just over-active sanity check Index: ipa-devirt.c === --- ipa-devirt.c (revision 207588) +++ ipa-devirt.c

[Bug c/60103] Spurious -Wsequence-point warning with -O1

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60103 --- Comment #2 from Chengnian Sun chengniansun at gmail dot com --- (In reply to Andrew Pinski from comment #1) I think C11 and C90/C99 have a different idea here. There is a relative sequence point between the function call fn2 and the 0 but

[Bug ipa/59918] [4.9 Regression] ICE in record_target_from_binfo, at ipa-devirt.c:693

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59918 --- Comment #9 from Jan Hubicka hubicka at gcc dot gnu.org --- Author: hubicka Date: Fri Feb 7 06:01:36 2014 New Revision: 207592 URL: http://gcc.gnu.org/viewcvs?rev=207592root=gccview=rev Log: PR ipa/59918 * ipa-devirt.c

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #21 from Jouko Orava jouko.orava at iki dot fi --- This bug is a duplicate of #55916.

[Bug preprocessor/56824] [4.8/4.9 regression] pragma GCC diagnostic push/pop fail with GCC diagnostic ignored -Waggregate-return

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56824 --- Comment #9 from Magnus Reftel magnus.reftel at gmail dot com --- Thanks for the patch! I applied it on top of 53c3c39b96df9c6a6368bf0d6acfd28a7af3cb63 and tested. Without the patch, the error was still printed when compiling the testcase.

[Bug target/40977] [4.7/4.8/4.9 regression] problem with code like this: res = ((uint64_t)resh 32) | resl;

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40977 Jeffrey A. Law law at redhat dot com changed: What|Removed |Added Status|UNCONFIRMED |NEW Last

[Bug c++/60105] New: [C++11] g++ segfault on enable_if explicit cast operator

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60105 Bug ID: 60105 Summary: [C++11] g++ segfault on enable_if explicit cast operator Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal

[Bug c++/60106] New: ICE in g++.dg/gomp/pr59150.C

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60106 Bug ID: 60106 Summary: ICE in g++.dg/gomp/pr59150.C Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

<    1   2