public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dimitry at andric 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 19:46:03 +0000	[thread overview]
Message-ID: <bug-101491-4-RjHCApTm3D@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

--- Comment #4 from Dimitry Andric <dimitry at andric dot com> ---
(In reply to Gerald Pfeifer from comment #3)
> (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?

Yes, it's only the FreeBSD gcc 11 and 12 ports that have these headers. But
indeed they have been provided by gcc's Makefiles since 2014.

  parent reply	other threads:[~2021-07-18 19:46 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
2021-07-18 19:46 ` dimitry at andric dot com [this message]
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-RjHCApTm3D@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).