On 4/6/24 4:54 PM, Neil Carlson wrote:
What are the recommended options to use (e.g., --enable-libsanitize)
when building GCC from source for the purpose of locating gfortran bugs?
I'm trying to pin down a runtime memory corruption error, and I recall
seeing at various times in the past recommendations for creating a
suitable gfortran build and the associated gfortran command line options
for dumping internal info, but I can't seem to find that info now.
Thanks!
I use this:
#! /bin/bash
rm -rf /home/jerry/dev/objdir/*
cd /home/jerry/dev/objdir
../trunk/configure --prefix=/home/jerry/dev/usr
--enable-languages=c,c++,fortran --enable-libgomp --disable-
bootstrap --enable-valgrind-annotations
make -j10 1>/dev/null && make install 1>/dev/null
echo "Build of trunk complete.."
-fdump-tree-original is one of the options if you intend to do front-end
work.
More info here:
Must read links for new developers/contributors:
https://gcc.gnu.org/fortran/
https://www.gnu.org/prep/standards/standards.html
https://gcc.gnu.org/gitwrite.html
https://gcc.gnu.org/wiki/GFortranHacking
https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gccint/
