On Thu, 6 Dec 2018, Florian Weimer wrote:
> > I seem to remember having to take extra care with how the three MIPS ABIs
> > wire the syscalls to get it right in glibc, but I take it then this has
> > been now addressed reliably enough for the glibc not to care how exactly
> > has been arranged
* Maciej W. Rozycki:
> On Thu, 6 Dec 2018, Joseph Myers wrote:
>
>> > So how are `SYS_' macros generated that land in ?
>>
>> By gen-syscall-h.awk, which generates #ifdef conditionals for each
>> possible __NR_* name (as listed in syscall-names.list in glibc).
>
> I seem to remember having to
On Thu, 6 Dec 2018, Joseph Myers wrote:
> > So how are `SYS_' macros generated that land in ?
>
> By gen-syscall-h.awk, which generates #ifdef conditionals for each
> possible __NR_* name (as listed in syscall-names.list in glibc).
I seem to remember having to take extra care with how the thr
On Thu, 6 Dec 2018, Maciej W. Rozycki wrote:
> On Thu, 6 Dec 2018, Joseph Myers wrote:
>
> > > I believe this file is used by the glibc build process to retrieve
> > > syscall numbers for glibc's own use as well for . Has the
> > > change been verified not to break this process?
> > >
> > >
On Thu, 6 Dec 2018, Joseph Myers wrote:
> > I believe this file is used by the glibc build process to retrieve
> > syscall numbers for glibc's own use as well for . Has the
> > change been verified not to break this process?
> >
> > Cc-ing for information and possible further
> > input.
>
On Thu, 6 Dec 2018, Maciej W. Rozycki wrote:
> I believe this file is used by the glibc build process to retrieve
> syscall numbers for glibc's own use as well for . Has the
> change been verified not to break this process?
>
> Cc-ing for information and possible further
> input.
I'm not
6 matches
Mail list logo
