[Bug c/85320] New: Segmentation fault when building XKAAPI

2018-04-10 Thread jules at penuchot dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85320

Bug ID: 85320
   Summary: Segmentation fault when building XKAAPI
   Product: gcc
   Version: 7.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
  Assignee: unassigned at gcc dot gnu.org
  Reporter: jules at penuchot dot com
  Target Milestone: ---

I get a segmentation fault when I build XKAAPI ver. 3.1.1rc01 with GCC 7.2.0 on
Ubuntu 17.04 on a Dell XPS 13 (i7 6560U, 8GB RAM)

Here's the link to XKAAPI:
http://kaapi.gforge.inria.fr/

The link to the specific version:
https://gforge.inria.fr/frs/download.php/zip/10051/xkaapi-3.1.1rc01.zip

And there's the error message:

In file included from kaapi++:51:0,
 from ka_error.cpp:48:
kaapi++.h: In static member function ‘static const kaapi_format_t*
ka::WrapperFormat::get_c_format()’:
kaapi++.h:279:27: internal compiler error: Segmentation fault
 return format.Format::get_c_format();
   ^~~~

Just after these two lines:

/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../..  -I../../src -I.   -Wall -g -O2  -std=c++0x -pedantic  -MT
libkaapi___la-ka_error.lo -MD -MP -MF .deps/libkaapi___la-ka_error.Tpo -c -o
libkaapi___la-ka_error.lo `test -f 'ka_error.cpp' || echo './'`ka_error.cpp

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I../../src -I. -Wall -g -O2
-std=c++0x -pedantic -MT libkaapi___la-ka_error.lo -MD -MP -MF
.deps/libkaapi___la-ka_error.Tpo -c ka_error.cpp  -fPIC -DPIC -o
.libs/libkaapi___la-ka_error.o

[Bug other/92396] -ftime-trace support

2021-10-15 Thread jules at penuchot dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92396

Jules Pénuchot  changed:

   What|Removed |Added

 CC||jules at penuchot dot com

--- Comment #10 from Jules Pénuchot  ---
I've been writing a compile-time benchmarking and analysis tool
(https://github.com/JPenuchot/ctbench) to study the impact of C++
metaprogramming techniques on compile-times. Clang's time-trace features allows
me to break the measurements down to every major compiler pass and get a better
understanding of what's happening under the hood.

I'd be really happy if GCC provided similar profiling tools and draw
conclusions that aren't valid just for Clang.