[Bug c++/98538] [11 Regression] ICE in cp_build_qualified_type_real, at cp/tree.c:1335

2021-01-15 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98538 --- Comment #8 from Marek Polacek --- (In reply to Nathan Sidwell from comment #5) > I don;t think your patch is quite right. the call afterwards is making the > assumption that DEPENDENT_TYPE_P is only ever set when > DEPENDENT_TYPE_P_VALID is

[Bug c++/96623] [11 Regression] ICE in inject_parm_decls, at cp/parser.c:23893

2021-01-15 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96623 Marek Polacek changed: What|Removed |Added Status|NEW |ASSIGNED Keywords|ice-on-inval

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org --- C

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #2

[Bug d/98607] GDC merging computations but rounding mode has changed

2021-01-15 Thread glisse at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98607 --- Comment #9 from Marc Glisse --- Since I doubt gdc handles rounding modes correctly for scalars, I think you can ignore this issue in the implementation of the vector intrinsics for now (same as we do in C and C++). Note that gcc isn't alone

[Bug rtl-optimization/98692] Unitialized Values reported only with -Os

2021-01-15 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692 --- Comment #4 from Segher Boessenkool --- Are you sure that target is correct?!

[Bug rtl-optimization/98692] Unitialized Values reported only with -Os

2021-01-15 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692 Segher Boessenkool changed: What|Removed |Added CC||acsawdey at gcc dot gnu.org --- Com

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread Bahram.shahrooz at uc dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #3 from Bahram.shahrooz at uc dot edu --- Created attachment 49979 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49979&action=edit source code Sorry, I had to zip several files. Readme file in Archive.zip explains what the file

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread Bahram.shahrooz at uc dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #4 from Bahram.shahrooz at uc dot edu --- I compiled with the suggested options (below) and now the code gives the same result as g77. -fcheck=all -ffpe-trap=zero,invalid Things look good now! Sorry for starting this bug report prem

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread sgk at troutmask dot apl.washington.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #5 from Steve Kargl --- On Sat, Jan 16, 2021 at 12:41:56AM +, Bahram.shahrooz at uc dot edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 > > --- Comment #4 from Bahram.shahrooz at uc dot edu --- > I compiled with t

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread Bahram.shahrooz at uc dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #6 from Bahram.shahrooz at uc dot edu --- I get wrong answers doing this: gfortran FiberAnalysis.f -o FiberAnalysis I get correct answers doing this: gfortran FiberAnalysis.f -fcheck=all -ffpe-trap=zero,invalid -o FiberAnalysis

[Bug middle-end/98702] New: linker failure with a very simple testing case for gcc10

2021-01-15 Thread qinzhao at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98702 Bug ID: 98702 Summary: linker failure with a very simple testing case for gcc10 Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Prio

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread sgk at troutmask dot apl.washington.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #7 from Steve Kargl --- On Sat, Jan 16, 2021 at 12:51:38AM +, Bahram.shahrooz at uc dot edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 > > --- Comment #6 from Bahram.shahrooz at uc dot edu --- > I get wrong answe

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread sgk at troutmask dot apl.washington.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #8 from Steve Kargl --- On Fri, Jan 15, 2021 at 05:21:22PM -0800, Steve Kargl wrote: > > You're using undefined variables. > I little more debugging, read(5,*) estrt,esfinal,eincr if(eincr.gt.0) xnumber=(esfinal-estar

[Bug tree-optimization/98703] New: Failure to optimize out non-zero check relative to multiplication overflow check

2021-01-15 Thread gabravier at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98703 Bug ID: 98703 Summary: Failure to optimize out non-zero check relative to multiplication overflow check Product: gcc Version: 11.0 Status: UNCONFIRMED Severity:

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread Bahram.shahrooz at uc dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #9 from Bahram.shahrooz at uc dot edu --- Yes, thank you for finding this bug. Things didn't change after changing estart to estrt. Sorry, I don't know how to use -freal-init=nan. I tried to use it like this but got an error. % gfo

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

2021-01-15 Thread sgk at troutmask dot apl.washington.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #10 from Steve Kargl --- On Sat, Jan 16, 2021 at 04:48:09AM +, Bahram.shahrooz at uc dot edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 > > --- Comment #9 from Bahram.shahrooz at uc dot edu --- > Yes, thank you f

<    1   2