On Mon, Feb 21, 2022 at 1:02 PM Richard Biener
wrote:
>
> On Sun, Feb 20, 2022 at 11:44 PM Andrew Pinski via Gcc
> wrote:
> >
> > On Sun, Feb 20, 2022 at 10:45 AM Shubham Narlawar
> > wrote:
> > >
> > > On Sat, Feb 19, 2022 at 1:15 AM Andrew Pinski wrote:
> > > >
> > > > On Fri, Feb 18, 2022
That's true, I did notice GCC being rather ... peculiar about
drhystone. Is there a way to make it less clever about the benchmark?
Or is there some alteration to the benchmark I can make to not trigger
the special behavior in GCC?
Andras
On Mon, 2022-02-21 at 03:19 +, Gary Oblock via Gcc wr
To GCC team,
We sent the follow message two weeks ago, buy didn't get response yet.
So, send this again and sorry for the inconvenience ~
>>>
I'm Ceasar Sun , from Free Software Lab, NCHC , Taiwan.
We provide several free software mirror service in Taiwan :
free.nchc.org.tw
We would like t
On Sun, 2022-02-20 at 12:19 +0100, Thomas Schwinge wrote:
> Hi David!
>
> On 2022-01-07T12:41:17-0500, David Malcolm via Fortran <
> fort...@gcc.gnu.org> wrote:
> > I'd like to (again) mentor a project relating to the GCC static
> > analyzer:
> > https://gcc.gnu.org/wiki/DavidMalcolm/StaticAnal
