public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/107078] LTO is causing that firebird build is core dumping
Date: Sat, 03 Dec 2022 10:08:31 +0000 [thread overview]
Message-ID: <bug-107078-4-p83xs5Vlay@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107078-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107078
Sam James <sam at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sam at gentoo dot org
--- Comment #19 from Sam James <sam at gentoo dot org> ---
I get some ODR warnings in gpre:
```
/tmp/firebird/Firebird-4.0.2.2816-0/src/gpre/pat.cpp:60:21: warning: type
‘struct ops’ violates the C++ One Definition Rule [-Wodr]
60 | static const struct ops
| ^
/tmp/firebird/Firebird-4.0.2.2816-0/src/gpre/sqe.cpp:124:8: note: a different
type is defined in another translation unit
124 | struct ops
| ^
/tmp/firebird/Firebird-4.0.2.2816-0/src/gpre/pat.cpp:62:15: note: the first
difference of corresponding definitions is field ‘ops_type’
62 | pat_t ops_type;
| ^
/tmp/firebird/Firebird-4.0.2.2816-0/src/gpre/sqe.cpp:126:15: note: a field with
different name is defined in another translation unit
126 | nod_t rel_op;
| ^
lto-wrapper: warning: using serial compilation of 11 LTRANS jobs
lto-wrapper: note: see the ‘-flto’ option documentation for more information
rm -f /tmp/firebird/Firebird-4.0.2.2816-0/gen/Release/firebird/bin/gpre_current
```
--
Anyway, as a hack, try this:
```
diff --git a/gen/Makefile b/gen/Makefile
index a121c31..8eabd44 100644
--- a/gen/Makefile
+++ b/gen/Makefile
@@ -438,7 +438,7 @@ yachts.lnk: metadata.fdb
metadata.fdb: $(RUN_ISQL) $(SRC_ROOT)/dbs/metadata.sql
-$(RM) $@
- $(RUN_ISQL) -q -i $(SRC_ROOT)/dbs/metadata.sql
+ gdbserver 127.0.0.1:1234 -- $(RUN_ISQL) -q -i
$(SRC_ROOT)/dbs/metadata.sql
$(RUN_GFIX) -mode read_only $@
$(CHMOD) 0444 $@
@@ -467,9 +467,9 @@ security.fdb: $(SRC_ROOT)/dbs/security.sql
msg.timestamp: $(MSG_FILES)
-$(RM) msg.fdb
- echo create database \'msg.fdb\'\; | $(RUN_ISQL)
+ echo create database \'msg.fdb\'\; | gdbserver 127.0.0.1:1235 --
$(RUN_ISQL)
$(RUN_GFIX) -write async msg.fdb
- for sql in $(MSG_FILES); do (echo $$sql; $(RUN_ISQL) -i $$sql msg.fdb)
|| exit; done
+ for sql in $(MSG_FILES); do (echo $$sql; gdbserver 127.0.0.1:1236 --
$(RUN_ISQL) -i $$sql msg.fdb) || exit; done
$(TOUCH) $@
```
next prev parent reply other threads:[~2022-12-03 10:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 21:51 [Bug lto/107078] New: " kloczko.tomasz at gmail dot com
2022-09-28 22:06 ` [Bug lto/107078] " pinskia at gcc dot gnu.org
2022-09-28 22:08 ` pinskia at gcc dot gnu.org
2022-09-29 8:20 ` rguenth at gcc dot gnu.org
2022-09-29 10:20 ` marxin at gcc dot gnu.org
2022-09-29 10:52 ` kloczko.tomasz at gmail dot com
2022-09-29 11:00 ` pinskia at gcc dot gnu.org
2022-09-29 11:01 ` jakub at gcc dot gnu.org
2022-09-29 11:04 ` kloczko.tomasz at gmail dot com
2022-09-29 11:09 ` kloczko.tomasz at gmail dot com
2022-09-29 11:21 ` kloczko.tomasz at gmail dot com
2022-09-29 11:24 ` kloczko.tomasz at gmail dot com
2022-11-01 15:00 ` kloczko.tomasz at gmail dot com
2022-11-10 14:17 ` marxin at gcc dot gnu.org
2022-12-02 13:38 ` marxin at gcc dot gnu.org
2022-12-02 16:53 ` kloczko.tomasz at gmail dot com
2022-12-02 18:27 ` marxin at gcc dot gnu.org
2022-12-02 18:53 ` kloczko.tomasz at gmail dot com
2022-12-02 19:04 ` marxin at gcc dot gnu.org
2022-12-03 10:08 ` sam at gentoo dot org [this message]
2022-12-05 9:56 ` marxin at gcc dot gnu.org
2022-12-05 12:23 ` kloczko.tomasz at gmail dot com
2022-12-05 12:27 ` sam at gentoo dot org
2022-12-05 12:32 ` marxin at gcc dot gnu.org
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=bug-107078-4-p83xs5Vlay@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).