public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/101491] [11 regression] /usr/local/include/libgccjit++.h conflicts between different GCC installations
Date: Sun, 18 Jul 2021 14:13:27 +0000 [thread overview]
Message-ID: <bug-101491-4-VjCXFn43m9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101491-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491
Gerald Pfeifer <gerald at pfeifer dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-07-18
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #3 from Gerald Pfeifer <gerald at pfeifer dot com> ---
As one data point, gccjit is a "relatively newer" thing for the FreeBSD
ports of GCC, e.g. in case of lang/gcc11-devel:
commit bb995aaf6e25e33b028fa4b32321864b48f49055
Author: Ashish SHUKLA <ashish@FreeBSD.org>
Date: Tue Feb 23 09:07:37 2021 +0000
- Enable gccjit support
Approved by: gerald (maintainer)
Looking at the diff it appears the issue was there back then already:
--- a/lang/gcc11-devel/pkg-plist
+++ b/lang/gcc11-devel/pkg-plist
@@ -18,6 +18,8 @@ bin/gcov-dump%%SUFFIX%%
bin/gcov-tool%%SUFFIX%%
bin/gfortran%%SUFFIX%%
bin/lto-dump%%SUFFIX%%
+include/libgccjit++.h
+include/libgccjit.h
Alas it only materialized when lang/gcc12-devel was added:
commit 982ce2ea27d8d41ed4f69c6c8f1eb56f04280531
Author: Gerald Pfeifer <gerald@FreeBSD.org>
Date: Mon May 3 10:45:02 2021 +0000
lang/gcc12-devel: New port based on the 20210426 snapshot of GCC 12.0.0
This is the first snapshot from trunk with the GCC 12 designation. It
largely is a copy of lang/gcc11-devel.
(In reply to David Malcolm from comment #2)
> I wonder why this changed recently; as Dimitry notes, this has been
> done the same since the initial merger of libgccjit into trunk.
I believe we are not looking at a regression in one of the FreeBSD ports
nor on the gccjit side, just an issue that's been there "from day 1".
Dimitry, is this consistent with your experience?
> I'm using $(includedir). What should I be using? Thanks
I'm not an expert, yet dug a bit and most include files appear to be
installed in lib/gcc11/gcc/i386-portbld-freebsd11.4/11.1.1/include
which libgomp/Makefile, libquadmath/Makefile, libssp/Makefile and
others have as
libsubincludedir = $(libdir)/gcc/$(target_alias)/$(gcc_version)/include
Would something like this work for libgccjit as well, David?
next prev parent reply other threads:[~2021-07-18 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 20:29 [Bug jit/101491] New: " gerald at pfeifer dot com
2021-07-17 21:22 ` [Bug jit/101491] " dimitry at andric dot com
2021-07-17 23:08 ` dmalcolm at gcc dot gnu.org
2021-07-18 14:13 ` gerald at pfeifer dot com [this message]
2021-07-18 19:46 ` dimitry at andric dot com
2021-07-19 6:35 ` [Bug jit/101491] [11/12 " rguenth at gcc dot gnu.org
2021-07-28 7:07 ` rguenth at gcc dot gnu.org
2021-09-26 9:08 ` gerald at pfeifer dot com
2022-01-20 12:47 ` [Bug jit/101491] " rguenth at gcc dot gnu.org
2022-11-04 20:31 ` rv4chsst7e at liamekaens dot com
2022-11-04 20:35 ` rv4chsst7e at liamekaens dot com
2022-11-04 21:40 ` rv4chsst7e at liamekaens dot com
2022-11-16 16:06 ` developer at lorenzosalvadore dot it
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-101491-4-VjCXFn43m9@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).