[Bug rtl-optimization/91332] ICE: Segfault in gfortran when compiling massive subroutine with -O3

2020-03-01 Thread clogged.drainpipe at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91332

--- Comment #3 from Madarpok .  ---
Any movement regarding this?

[Bug fortran/91332] New: ICE: Segfault in gfortran when compiling massive function with -O3

2019-08-02 Thread clogged.drainpipe at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91332

Bug ID: 91332
   Summary: ICE: Segfault in gfortran when compiling massive
function with -O3
   Product: gcc
   Version: 7.4.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
  Assignee: unassigned at gcc dot gnu.org
  Reporter: clogged.drainpipe at gmail dot com
  Target Milestone: ---

Created attachment 46664
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46664&action=edit
gzipped source to reproduce

Hello!

We have run into an ICE when we tried to compile an admittedly pretty massive
subroutine. I am not sure which component is segfaulting, so for lack of better
idea I am filing this under gfortran, please feel free to reassign it as you
see fit. The system is running Ubuntu 18.04 LTS. Gfortran just throws an ICE
segfault after about an hour of wall time. Please note that gfortran also
consumes ~60+ GiB of RAM before finally segfaulting. I tested on a machine that
has 64 GiB of RAM and some swap on an SSD, and apart from the segfault I had no
issues, but with less RAM this might be challenging to reproduce.

The command line that causes the crash is:
gfortran -v -O3 -march=skylake -ffree-line-length-0 -save-temps -c dmono_4.f90

Interestingly, there is no crash with O0,O1 or even O2. I am yet to test other
optimization levels. Not much else can I say about this, but if anyone needs
more info, please do ask.

Complete output of the command line above:

Using built-in specs.
COLLECT_GCC=gfortran
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
COLLECT_GCC_OPTIONS='-v' '-O3' '-march=skylake' '-ffree-line-length-0'
'-save-temps' '-c'
 /usr/lib/gcc/x86_64-linux-gnu/7/f951 dmono_4.f90 -quiet -dumpbase dmono_4.f90
-march=skylake -auxbase dmono_4 -O3 -version -ffree-line-length-0
-fintrinsic-modules-path /usr/lib/gcc/x86_64-linux-gnu/7/finclude -o dmono_4.s
GNU Fortran (Ubuntu 7.4.0-1ubuntu1~18.04.1) version 7.4.0 (x86_64-linux-gnu)
compiled by GNU C version 7.4.0, GMP version 6.1.2, MPFR version 4.0.1,
MPC version 1.1.0, isl version isl-0.19-GMP

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU Fortran2008 (Ubuntu 7.4.0-1ubuntu1~18.04.1) version 7.4.0
(x86_64-linux-gnu)
compiled by GNU C version 7.4.0, GMP version 6.1.2, MPFR version 4.0.1,
MPC version 1.1.0, isl version isl-0.19-GMP

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
dmono_4.f90:19736:0:

   end subroutine devmono_4

internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.

[Bug rtl-optimization/91332] ICE: Segfault in gfortran when compiling massive subroutine with -O3

2019-08-07 Thread clogged.drainpipe at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91332

--- Comment #2 from Madarpok .  ---
I can confirm that raising the stack limit with ulimit -s unlimited does not
prevent this crash.
Something inside gfortran is breaking/overflowing.

[Bug web/117309] New: [Docs] C++23 is not mentioned on the "supported standards" doc page

2024-10-26 Thread clogged.drainpipe at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117309

Bug ID: 117309
   Summary: [Docs] C++23 is not mentioned on the "supported
standards" doc page
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: web
  Assignee: unassigned at gcc dot gnu.org
  Reporter: clogged.drainpipe at gmail dot com
  Target Milestone: ---

I think https://gcc.gnu.org/onlinedocs/gcc/Standards.html should mention the
status of C++23 support in GCC. Currently there are zero hits for "C++23" on
the page, which does not feel correct given that most of it has been
implemented.

[Bug c++/117309] [Docs] C++23 is not mentioned on the "supported standards" doc page

2024-10-26 Thread clogged.drainpipe at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117309

--- Comment #2 from Madarpok .  ---
(In reply to Andrew Pinski from comment #1)
> Well c++23 was only published within the last month.

Hmm, fair enough. -std=c++2b has been supported for quite a while, but I see
your point.

[Bug web/118159] New: [Docs][Link rot] Fortran coco is now an online casino

2024-12-20 Thread clogged.drainpipe at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118159

Bug ID: 118159
   Summary: [Docs][Link rot] Fortran coco is now an online casino
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: web
  Assignee: unassigned at gcc dot gnu.org
  Reporter: clogged.drainpipe at gmail dot com
  Target Milestone: ---

On this docs page:
https://gcc.gnu.org/onlinedocs/gfortran/Preprocessing-Options.html
users are pointed to get the coco program for Conditional Compilation
preprocessing from this URL:
http://www.daniellnagle.com/coco.html

Unfortunately, this URL has succumbed to link rot, the domain has likely
expired at some point and is currently used by an online casino.

[Bug fortran/118161] New: Better preprocessing in gfortran

2024-12-20 Thread clogged.drainpipe at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118161

Bug ID: 118161
   Summary: Better preprocessing in gfortran
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
  Assignee: unassigned at gcc dot gnu.org
  Reporter: clogged.drainpipe at gmail dot com
  Target Milestone: ---

The state of preprocessing is not great in Fortran. Coco is dead and gone, and
nothing got standardized instead. Gfortran supports running the C preprocessor
in "traditional" mode, where it emulates the behavior of ancient pre-89 C
preprocessors to not step on the toes of any Fortran source files.

This is unfortunate for me, as I am using a preprocessor feature (concatenation
with ##) that is only in C89 and later, forcing me to run
cpp -P -std=c89 interface.F08 | gfortran ...
instead of simply telling gfortran to use a different preprocessing standard.

This works at the moment, but not really ideal. I am lucky enough to be able to
write the few Fortran files I need the preprocessor for with statements that do
not get broken by -std=c89, but I feel like there ought to be some better way.