> On 22 Jun 2018, at 22:39, Jeff Law wrote:
>> +@item -nolibc
>> +@opindex nolibc
>> +Do not use the C library or system libraries tightly couple with it when
> s/tightly couple/ that tightly couple/
>
> or
>
> s/couple/coupled/
>
> OK with either of those trivial fixes.
Great, Thanks Jeff
On 06/21/2018 11:06 AM, Olivier Hainque wrote:
> Hello Joseph,
>
> Thanks for getting back to me on this!
>
>> On 19 Jun 2018, at 17:50, Joseph Myers wrote:
>>
>> On Thu, 7 Jun 2018, Olivier Hainque wrote:
>>
>>> An updated version of the patch is attached, accounting for
>>> your two comments a
Hello Joseph,
Thanks for getting back to me on this!
> On 19 Jun 2018, at 17:50, Joseph Myers wrote:
>
> On Thu, 7 Jun 2018, Olivier Hainque wrote:
>
>> An updated version of the patch is attached, accounting for
>> your two comments and expanding on the .texi documentation a
>> bit.
>
> I s
On Thu, 7 Jun 2018, Olivier Hainque wrote:
> An updated version of the patch is attached, accounting for
> your two comments and expanding on the .texi documentation a
> bit.
I see you're not changing LINK_GCC_C_SEQUENCE_SPEC in arc/elf.h. That's a
slightly odd case in that it isn't actually u
Hello Joseph,
This is a follow up on an exchange you had with Tristan Gingold
back in Aug. 2017, starting from
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01824.html
with your answer on his proposal at:
https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00166.html
(Tristan has moved to other
On Thu, 27 Jul 2017, Tristan Gingold wrote:
> Index: gcc/common.opt
> ===
> --- gcc/common.opt(revision 250563)
> +++ gcc/common.opt(working copy)
> @@ -2956,6 +2956,10 @@
> nostdlib
> Driver
>
> +nolibc
> +Driver
> +Do not
Hello,
this patch adds a new option -nolibc to supress -lc in the link command.
This refines -nostdlib/-nostartfiles/nodefaultlibs, so that it is
possible to link with libgcc but without libc.
Our main use case is for embedded targets when we use the GNAT compiler
without an installed libc.
