public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Alexander Fedotov <alfedotov@gmail.com>
To: Tamar Christina <Tamar.Christina@arm.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>, nd <nd@arm.com>
Subject: Re: [AArch64] nosys.specs and printf
Date: Fri, 06 Oct 2017 15:44:00 -0000	[thread overview]
Message-ID: <CAN8C2CoL5VppD81cr9oLGS9xeV5yTs9KpDiWKeDznhJWy0v-4A@mail.gmail.com> (raw)
In-Reply-To: <DB6PR0802MB2309C11848AB86F6761A5DC4FF7D0@DB6PR0802MB2309.eurprd08.prod.outlook.com>

ping

On Mon, Oct 2, 2017 at 1:01 PM, Tamar Christina <Tamar.Christina@arm.com> wrote:
> Hi Alex,
>
> Thanks, looks good to me,
> but I can't approve for newlib, so a maintainer will have to take a look.
>
> Regards,
> Tamar
>
>> -----Original Message-----
>> From: Alexander Fedotov [mailto:alfedotov@gmail.com]
>> Sent: 29 September 2017 20:16
>> To: Tamar Christina
>> Cc: newlib@sourceware.org; nd
>> Subject: Re: [AArch64] nosys.specs and printf
>>
>> Here is a patch to correct libnosys configuration for aarch64.
>> Linker warning still be emitted as agreed.
>>
>> Alex
>>
>> On Fri, Sep 22, 2017 at 11:05 AM, Tamar Christina
>> <Tamar.Christina@arm.com> wrote:
>> >
>> >
>> >> -----Original Message-----
>> >> From: Alexander Fedotov [mailto:alfedotov@gmail.com]
>> >> Sent: 20 September 2017 16:24
>> >> To: Jon Beniston
>> >> Cc: Tamar Christina; newlib@sourceware.org; nd
>> >> Subject: Re: [AArch64] nosys.specs and printf
>> >>
>> >> >>That's not doing anything other than setting errno to ENOSYS to
>> >> >>indicate
>> >> it's not available.
>> >> Yes the same as ARM.
>> >>
>> >> So to sum up. We have several points:
>> >> 1. ARM port doesn't warn user about missing _write(). While this
>> >> function is present in final ELF and does nothing.
>> >> 2. AArch64 warns "warning: _write() is not implemented and will always
>> fail"
>> >> while _write() it is present in ELF.
>> >
>> > Both of these are probably correct, while I consider the ARM behaviour
>> > to be the incorrect one It may be so for historical reasons. I'm not really
>> sure.
>> >
>> >> 3. libnosys has inconsistent configuration against rdimon. It is
>> >> impossible to switch between rdimon.specs and nosys.specs.
>> >
>> > I don't quite get what you mean with this, but I assume you mean that
>> > using nosys.specs with AArch64 Results in link errors if you use I/O. Again
>> this is because we don't support nosys for AArch64.
>> >
>> > That said, a patch to have libnosys compile (with warnings) for AArch64
>> would be fine.
>> >
>> > Tamar.
>> >>
>> >> Thoughts ?
>> >>
>> >> Alex
>> >>
>> >> On Wed, Sep 20, 2017 at 5:08 PM, Jon Beniston <jon@beniston.com>
>> wrote:
>> >> >> Well at least _write is here:
>> >> >
>> >> > That's not doing anything other than setting errno to ENOSYS to
>> >> > indicate it's
>> >> not available.
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Best regards,
>> >> AF
>>
>>
>>
>> --
>> Best regards,
>> AF



-- 
Best regards,
AF

  reply	other threads:[~2017-10-06 11:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19  6:21 Alexander Fedotov
2017-09-19 17:43 ` Tamar Christina
     [not found]   ` <CAN8C2Crygk-MsBz-=x5qa0pJ-2SvOQoOwdqcJztxppdTskEkdg@mail.gmail.com>
     [not found]     ` <DB6PR0802MB23090588EC607014E69E9B1AFF600@DB6PR0802MB2309.eurprd08.prod.outlook.com>
     [not found]       ` <CAN8C2CoX3aHHe2WixnQM1eHzigdLgb4A44v=BQj2Cs60tmmUHw@mail.gmail.com>
2017-09-20 13:40         ` Alexander Fedotov
2017-09-20 14:03           ` Tamar Christina
2017-09-20 14:08             ` Alexander Fedotov
2017-09-20 15:24               ` Jon Beniston
2017-09-22  8:06                 ` Alexander Fedotov
2017-09-22  9:50                   ` Tamar Christina
2017-10-02 10:01                     ` Alexander Fedotov
2017-10-05 12:56                       ` Tamar Christina
2017-10-06 15:44                         ` Alexander Fedotov [this message]
2017-10-09 16:10                       ` Corinna Vinschen

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=CAN8C2CoL5VppD81cr9oLGS9xeV5yTs9KpDiWKeDznhJWy0v-4A@mail.gmail.com \
    --to=alfedotov@gmail.com \
    --cc=Tamar.Christina@arm.com \
    --cc=nd@arm.com \
    --cc=newlib@sourceware.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).