On 10/30/14 18:50, Joseph S. Myers wrote:
I don't see it as a blocker, but I would not be surprised if having the
libraries statically linked into libgccjit.so causes problems (is it safe
to have two completely separate copies of libstdc++ in the same process?
I don't know.).
Jason, Jakub, Aldy
On Thu, 30 Oct 2014, David Malcolm wrote:
> Looking at the build logs, I see:
> -fPIC
> within the xgcc args in the libgcc build logs, and
That seems to depend on t-libgcc-pic, but that appears to cover most
likely hosts (including any where I can be confident PIC is actually
needed for share
On Fri, 2014-10-17 at 21:52 +, Joseph S. Myers wrote:
> Does libgccjit.so end up getting linked with -static-libstdc++
> -static-libgcc?
(sorry for belated reply)
It does when built with a bootstrap, but doesn't with
--disable-bootstrap. In the former case, the builddir's gcc/Makefile in
th
Does libgccjit.so end up getting linked with -static-libstdc++
-static-libgcc? If so, that could be problematic (are static libstdc++
and libgcc necessarily built as PIC so it's even possible to embed them
into a shared library?). It's certainly not clear that the
-static-libstdc++ -static-li
On Tue, 2014-10-14 at 11:09 -0400, David Malcolm wrote:
> On Mon, 2014-10-13 at 13:45 -0400, David Malcolm wrote:
> > I'd like to merge the JIT branch into trunk:
> > https://gcc.gnu.org/wiki/JIT
> >
> > This is "v2" since it incorporates fixes for the various issues
> > identified by Joseph in
