public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: gcc-bugs@gcc.gnu.org
Cc: "team@refpersys.org" <team@refpersys.org>
Subject: Bug C++ 111974 (Segmentation fault of GCC, ubuntu 23.10, compiling RefPerSys 041d5d70aefd)
Date: Wed, 25 Oct 2023 11:38:51 +0200	[thread overview]
Message-ID: <6ccba6ad-2e4a-481e-9251-ebb13c407606@starynkevitch.net> (raw)

Hello all,


Sorry for this non-minimal bug report. I was unable to make a shorter or 
minimal bug example.

RefPerSys is a GPLv3+ open source project for an inference engine. See 
http://refpersys.org/ for ambitions and some details. (I am currently 
more interested in working on RefPerSys than on debugging GCC, to which 
I did contribute earlier). RefPerSys is itself on github in 
https://github.com/RefPerSys/RefPerSys/

I am compiling RefPerSys (mostly C++ code, including some self 
generated, which is including in the below snapshot) on Ubuntu 23.10 
whose g++ has version  (Ubuntu 13.2.0-4ubuntu3) 13.2.0 on a desktop with 
AMD Ryzen Threadripper 2970WX

The RefPerSys commit is 
https://github.com/RefPerSys/RefPerSys/commit/041d5d70aefd047de4eb456432853beefffb4120 
and has a few tests: eg make test00 test01 did work a few days ago.

I uploaded to 
http://refpersys.org/refpersys-gcc13bug-snapshot-25oct2023-git041d5d70aefd0.tar.bz2 
a bzip2 compressed tarball (29246912 bytes) of md5sum 
6b1d2985ce86bd1718d05af3d93a84f9

That tarball is likely to be removed in a few months.

The disk space for the RefPerSys source code (with object files) take 
less than 200 Mbytes.

To reproduce the GCC bug, run make (GNU make 4.3 from Ubuntu) in the tarball

If you did reproduce it, please email me (Basile Starynkevitch, in 
France) to basile@starynkevitch.net

Regards

-- 
Basile Starynkevitch
  <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/


                 reply	other threads:[~2023-10-25  9:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ccba6ad-2e4a-481e-9251-ebb13c407606@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=team@refpersys.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).