https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105710
--- Comment #8 from Iain Sandoe ---
(In reply to Eric Gallager from comment #7)
> > (as I have said several times, the idea of configure is to choose the
> > correct settings for the target _automatically_ - extra config options
> > should onl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
--- Comment #30 from Iain Sandoe ---
(In reply to Eric Gallager from comment #29)
> (In reply to Eric Gallager from comment #28)
> > (I recently got a new laptop and am now on Catalina and ran into this bug,
> > so that's why I'm coming back to i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80782
--- Comment #16 from Iain Sandoe ---
(In reply to Eric Gallager from comment #15)
> (In reply to Iain Sandoe from comment #12)
> > please could you be more specific about exactly what's not working?
> > - i.e if you're on an older version of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48626
--- Comment #5 from Iain Sandoe ---
(In reply to Eric Gallager from comment #4)
> (In reply to Eric Gallager from comment #3)
> > I'll probably keep --enable-objc-gc in my configure flags anyways even if it
> > becomes automatic, but becoming aut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665
--- Comment #5 from Iain Sandoe ---
(In reply to Eric Gallager from comment #4)
> Hm, looking in gcc/configure.ac (where these are defined), it looks like
> there's a bunch of other flags that this bug could apply to, too...
Note that I would t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48626
--- Comment #6 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #5)
> (In reply to Eric Gallager from comment #4)
> > (In reply to Eric Gallager from comment #3)
> > detecting things
> > automatically instead of requiring additio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719
Iain Sandoe changed:
What|Removed |Added
CC||iains at gcc dot gnu.org
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
--- Comment #33 from Iain Sandoe ---
(In reply to Eric Gallager from comment #32)
> (In reply to r...@cebitec.uni-bielefeld.de from comment #26)
> > That's one option, certainly easier for the users. At the least, the
> > issue should be documen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100340
--- Comment #33 from Iain Sandoe ---
(In reply to Richard Biener from comment #32)
> Unsure about GCC 10/11 status.
was fixed for 11, in my queue for 10.4 (time-willing)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100340
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80556
Iain Sandoe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104117
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100152
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101666
Iain Sandoe changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102992
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88414
Iain Sandoe changed:
What|Removed |Added
CC||iains at gcc dot gnu.org
--- Comment #7 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101718
--- Comment #7 from Iain Sandoe ---
still needed on 11.x.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100613
Iain Sandoe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101666
Iain Sandoe changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105599
--- Comment #6 from Iain Sandoe ---
needed on 11.x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106246
Bug ID: 106246
Summary: [13 Regression] powerpc-darwin9 bootstrap fails after
r13-1575-gcf3a120084e946 ICE vect_transform_loops, at
tree-vectorizer.cc:1032
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106246
Iain Sandoe changed:
What|Removed |Added
Keywords||build, ice-on-valid-code
Last reconfirm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106246
--- Comment #3 from Iain Sandoe ---
(In reply to Richard Biener from comment #2)
> Maybe a duplicate of PR106228. I can't reproduce with the fix for that in
> the tree. Is there anything besides --target=powerpc-darwin9 to use? Any
> -mcpu=?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106246
Iain Sandoe changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #5 from Iain Sandoe ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106246
--- Comment #6 from Iain Sandoe ---
as noted on IRC, of course this could be unrelated, since other changes have
been committed in the meantime.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106246
Iain Sandoe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283
--- Comment #3 from Iain Sandoe ---
(In reply to Indu Bhagat from comment #2)
> I see that .section directive needs a different semantic for Darwin. The
> DWARF debug_info section, for example, appears as:
>
> .section __DWARF,__debug_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283
--- Comment #5 from Iain Sandoe ---
(In reply to Richard Biener from comment #4)
> It might make sense to provide targets a means to opt-out of CTF/BTF support
> and thus diagnose -gctf as unsupported on them.
In the short-term, I've got fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283
--- Comment #8 from Iain Sandoe ---
we are now left with (where I suspect that the remaining fails are an artefact
of the way in which Darwin represents offsets instead of relocations in DWARF
debug sections):
Running target unix/-m64
Running
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283
--- Comment #9 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #8)
> we are now left with (where I suspect that the remaining fails are an
> artefact of the way in which Darwin represents offsets instead of
> relocations in DWARF debu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283
--- Comment #11 from Iain Sandoe ---
(In reply to Indu Bhagat from comment #10)
> (In reply to Iain Sandoe from comment #9)
> > (In reply to Iain Sandoe from comment #8)
> > > we are now left with (where I suspect that the remaining fails are an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100269
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101420
--- Comment #4 from Iain Sandoe ---
(In reply to Avi Kivity from comment #3)
> Adding Iain since the ICE happens in a coroutine. Meanwhile my desktop is
> reducing the testcase.
do you have a backtrace?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101420
--- Comment #6 from Iain Sandoe ---
(In reply to Avi Kivity from comment #5)
> How does one ask gcc to generate a backtrace on ICE?
It produces one when libbacktrace is available, not aware of needing to do
anything special; is there any other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101420
--- Comment #11 from Iain Sandoe ---
(In reply to Avi Kivity from comment #10)
> Reproduces on trunk:
>
> #7 0x00b439af in cp_build_modify_expr (loc=1376651745,
> lhs=0x7f0c55c12c60, modifycode=, rhs=0x7f0c55e63ee0,
> complain=) at ../
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101420
--- Comment #12 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #11)
> (In reply to Avi Kivity from comment #10)
> > Reproduces on trunk:
> this looks like a dup of PR 96056 - but I am happy to check the reduced case.
erm PR 98056 I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101420
Iain Sandoe changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98056
--- Comment #10 from Iain Sandoe ---
*** Bug 101420 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93758
--- Comment #5 from Iain Sandoe ---
(In reply to Mojca Miklavec from comment #4)
> I'm sorry, I forgot about this ticket. I can confirm that building (version
> 11.1) in fact works on all macOS versions at the moment
>
> https://ports.macports.o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100246
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100152
Iain Sandoe changed:
What|Removed |Added
Summary|[10/11/12 Regression] used |[10 Regression] used
|c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10
--- Comment #9 from Iain Sandoe ---
(In reply to Martin Liška from comment #8)
> Sure, but I would like to first speak Iain who added the code.
> What do you think about the patch?
hm, sorry for introducing the bash-ism, the change LGTM but I w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101616
Iain Sandoe changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10
--- Comment #10 from Iain Sandoe ---
(In reply to Mosè Giordano from comment #6)
> Created attachment 51038 [details]
> Patch to fix the reported issue
>
> Please find attached a patch to fix the reported issue. I replaced the
> bashism += wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101616
--- Comment #4 from Iain Sandoe ---
(In reply to Matt Jacobson from comment #3)
> As it happens, I'm targeting the NeXT v2 runtime, but I'm *not* actually
> targeting Darwin. So `flag_next_runtime` is just 1 for me--not an OS
> version value l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
Iain Sandoe changed:
What|Removed |Added
CC||iains at gcc dot gnu.org
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100340
--- Comment #11 from Iain Sandoe ---
(In reply to Matt Thompson from comment #10)
> Query from someone who I believe just encountered this trying to build 11.2
> on macOS 11.5.1 with XCode 12.5: What is the best method to work around this
> for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
Iain Sandoe changed:
What|Removed |Added
Target||x86_64-linux-gnu,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
Iain Sandoe changed:
What|Removed |Added
Summary|Weird memory corruption |[9/10/11/12 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100340
--- Comment #15 from Iain Sandoe ---
(In reply to Chris Jones from comment #14)
> Apologies, typo above. I meant to say the --without-build-config workaround
> no longer works with 11.2.0
OK.. I plan to do a Darwin/macOS 11.2 patch set this wee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84257
--- Comment #9 from Iain Sandoe ---
(In reply to Eric Gallager from comment #8)
> the MacPorts project applies the following patch to work around this issue:
> https://github.com/macports/macports-ports/commit/
> 0641e588e989b7b3e5049ca79e354339c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100340
--- Comment #20 from Iain Sandoe ---
I am testing a patch series (expected to push a github copy today if that
testing goes OK) including an implementation of comment #9.
However, IFF the jit build does not honour --without-build-config, that
a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101765
--- Comment #1 from Iain Sandoe ---
I am not sure that a VLA can be used in a coroutine (neither can alloca, if I
remember correctly) [so not sure that this is ICE on valid, it could be ICE on
invalid]
Either way, we should not ICE from it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100340
--- Comment #21 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #20)
> I rarely build the jit, but will take a look when time permits.
Actually, currently it seems that the JIT build is quite broken on Darwin; I
have some draft patc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101765
--- Comment #3 from Iain Sandoe ---
(In reply to Kacper Słomiński from comment #2)
> (In reply to Iain Sandoe from comment #1)
> > I am not sure that a VLA can be used in a coroutine (neither can alloca, if
> > I remember correctly) [so not sure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100613
Iain Sandoe changed:
What|Removed |Added
Assignee|dmalcolm at gcc dot gnu.org|iains at gcc dot gnu.org
Last re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101718
--- Comment #1 from Iain Sandoe ---
(In reply to Matt Jacobson from comment #0)
> When a method returns a type that the platform ABI says is returned in
> memory, the Objective-C frontend (for the NeXT runtime ABIs) emits a call to
> `objc_msgSe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95517
--- Comment #5 from Iain Sandoe ---
(In reply to mengjun wei from comment #4)
> GCC 11.2 no longer allow return_value and return_void be both defined, may
> this restriction be removed?
The restriction is part of the C++ standard (for the recor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101907
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98056
Iain Sandoe changed:
What|Removed |Added
CC||rcopley at gmail dot com
--- Comment #11 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101718
Iain Sandoe changed:
What|Removed |Added
Last reconfirmed||2021-08-16
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101718
Iain Sandoe changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100340
Iain Sandoe changed:
What|Removed |Added
Target Milestone|--- |9.5
--- Comment #23 from Iain Sandoe ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101666
Iain Sandoe changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43748
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112397
--- Comment #7 from Iain Sandoe ---
(In reply to Jakub Jelinek from comment #6)
> (In reply to Jonathan Wakely from comment #5)
> > Maybe:
> >
> > ifneq ($(filter %-darwin%,${host_alias}),)
>
> ${target_os} instead maybe?
I'll give that a try
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112397
--- Comment #10 from Iain Sandoe ---
automake if is limited to testing a single variable, so we have to introduce an
AM_CONDITIONAL to say the OS is DARWIN (we did not seem to have one already,
but I could have missed something else usable).
I'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113855
--- Comment #1 from Iain Sandoe ---
I was looking at making an i686 impl.
but we could also do as you suggest for gcc-14.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113855
--- Comment #3 from Iain Sandoe ---
(In reply to Jakub Jelinek from comment #2)
> Guess an ia32 implementation would be even better, shouldn't be that hard.
I have a draft on one of my machines, I'll post it here tomorrow.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113855
--- Comment #4 from Iain Sandoe ---
Created attachment 57378
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57378&action=edit
patch under test
This implements the common case for an i386 trampoline (and, in this respect,
matches the expec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112861
Iain Sandoe changed:
What|Removed |Added
Summary|[14 regression] Most gdc|Most gdc tests FAIL on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112862
Iain Sandoe changed:
What|Removed |Added
Summary|[14 regression] gfortran.dg |gfortran.dg coarray tests
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112863
Iain Sandoe changed:
What|Removed |Added
Summary|[14 regression] Many|Many obj-c++ tests FAIL on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112864
Iain Sandoe changed:
What|Removed |Added
Summary|[14 regression] Many|Many libphobos tests FAIL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110651
--- Comment #5 from Iain Sandoe ---
AFAICT, this was fixed on trunk by r14-6721-gd31c54c7da7661 (which seems to
have a reference to the PR so not sure why it did not show up here).
I think we need this on any open branch which we want to work w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113957
Bug ID: 113957
Summary: [14 Regression] bad-mapper-1.C hangs on all Darwin.
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113957
Iain Sandoe changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113957
--- Comment #1 from Iain Sandoe ---
the problem is that liberty is using the value set by posix_spawnp for pid.
but:
(darwin):
The argument pid is a pointer to a pid_t variable to receive the pid of
the spawned process; if this is NULL, th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113957
Iain Sandoe changed:
What|Removed |Added
Component|c++ |other
Keywords|wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105755
Iain Sandoe changed:
What|Removed |Added
Last reconfirmed||2024-02-16
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108562
Bug 108562 depends on bug 105755, which changed state.
Bug 105755 Summary: -Wanalyzer-null-dereference regression compiling Emacs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105755
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112294
Iain Sandoe changed:
What|Removed |Added
Target|x86_64-apple-darwin21 |x86_64-apple-darwin*
Build|x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113970
Bug ID: 113970
Summary: [14 Regression] pch/system-{1,2}.C fails on darwin
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: needs-bisection, wrong-code
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113970
Iain Sandoe changed:
What|Removed |Added
Last reconfirmed||2024-02-17
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113970
Iain Sandoe changed:
What|Removed |Added
Component|pch |c++
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113971
--- Comment #1 from Iain Sandoe ---
the intent was not to enable this feature for platforms we could not test.
but libgcc/config.host has "aarch64*-*-linux*" so we have inadvertently enabled
it for aarch64-linux-musl.
assuming linux-musl defin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113971
Iain Sandoe changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19779
--- Comment #9 from Iain Sandoe ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Sergey Fedorov from comment #6)
> > (In reply to Andrew Pinski from comment #0)
> > > This is the new bug for PR 19405. Keeping track of that we no lon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113957
Iain Sandoe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114007
Iain Sandoe changed:
What|Removed |Added
CC||fxcoudert at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114007
--- Comment #5 from Iain Sandoe ---
perhaps this is also a clang regression - for Jakub's example with Xcode 15.1 :
$ clang --version
Apple clang version 15.0.0 (clang-1500.1.0.2.5)
Target: x86_64-apple-darwin23.3.0
master-wip-short-queue mini
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114007
--- Comment #6 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #5)
> perhaps this is also a clang regression - for Jakub's example with Xcode
> 15.1 :
(xcode clang, that is, I did not test with upstream clang yet).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114007
--- Comment #10 from Iain Sandoe ---
indeed, it seems clang does not define __has_cpp_attribute for -std=c11 c
compilations, whereas GCC does.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114007
--- Comment #11 from Iain Sandoe ---
looking at n2176 - C18 there is no mention of __has_c*
looking at n3047 - C23 there is mention only of __has_c_attribute
OTOH, there is no prohibition in declaring __has_cpp_attribute (c.f. an actual
prohibi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114007
Iain Sandoe changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113971
Iain Sandoe changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107745
--- Comment #7 from Iain Sandoe ---
(In reply to Sebastian "spaetz" Spaeth from comment #5)
> I fully understand that nobody wants to invest time into fixing this. What
> would be nice though, is if this were really just a missed optimization an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114033
--- Comment #1 from Iain Sandoe ---
which actual SDK is this?
you should be able to look at the SDKsettings.plist in the root of the SDK, if
there's any need to discriminate versions with the same name.
(and is it possible to get pre-processed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114034
--- Comment #1 from Iain Sandoe ---
let me see if we're adding an extra in the Darwin specs that is covered
elsewhere (sometimes the specs get changed in gcc/gcc.cc and it takes us some
time to sync the ones in darwin.h)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036
--- Comment #1 from Iain Sandoe ---
yeah, there is a better way to do this with ld64 (and presumably dyld-ld), my
guess is that this is an anachronism from the ld_classic (v1) days.
We can tell the linker it's OK for a symbol to be undefined -
601 - 700 of 1271 matches
Mail list logo