[PATCH] aarch64: update NEWS about branch protection

[Szabolcs Nagy]

The 07/31/2020 07:58, Szabolcs Nagy wrote:
> The 07/29/2020 10:17, Szabolcs Nagy wrote:
> > The 07/29/2020 11:01, Florian Weimer wrote:
> > > * Szabolcs Nagy:
> > > > The 07/29/2020 10:11, Florian Weimer wrote:
> > > >> * Szabolcs Nagy:
> > > >> > diff --git a/NEWS b/NEWS
> > > >> > index 1ef4a0a7a4..0e6ad5edc4 100644
> > > >> > --- a/NEWS
> > > >> > +++ b/NEWS
> > > >> > @@ -70,7 +70,9 @@ Major new features:
> > > >> >  
> > > >> >  * AArch64 now supports standard branch protection security hardening
> > > >> >    in glibc when it is built with a GCC that is configured with
> > > >> > -  --enable-standard-branch-protection.  This includes branch target
> > > >> > +  --enable-standard-branch-protection (or if -mbranch-protection=standard
> > > >> > +  flag is passed when building both GCC target libraries and glibc,
> > > >> > +  in either case a custom GCC is needed).  This includes branch target
> > > >> >    identification (BTI) and pointer authentication for return addresses
> > > >> >    (PAC-RET).  They require armv8.5-a and armv8.3-a architecture
> > > >> >    extensions respectively for the protection to be effective,

Carlos, i think this NEWS update would be a useful
clarification, is there some concern about it?


> > > >> 
> > > >> Please clarify if you need to pass the flags in CFLAGS or CC for glibc.
> > > >> Thanks.
> > > >
> > > > cflags is enough, but it is hard to tell what
> > > > the glibc build system does with the various
> > > > cflags.
> > > >
> > > > if i simply override CFLAGS i get
> > > > # error "glibc cannot be compiled without optimization"
> > > 
> > > Okay, I trust you that CFLAGS is enough.
> ...
> > > My RM delegation has already expired, so I cannot approve your patch.
> > 
> > ok.
> 
> ping.
> 

--