On 10/30/20 4:08 AM, Stefan Schulze Frielinghaus wrote:
> On Wed, Oct 28, 2020 at 11:34:53AM -0600, Jeff Law wrote:
>> On 10/28/20 11:29 AM, Stefan Schulze Frielinghaus wrote:
>>> On Wed, Oct 28, 2020 at 08:39:41AM -0600, Jeff Law wrote:
On 10/28/20 3:38 AM, Stefan Schulze Frielinghaus via G
On 06.11.20 04:52, Jeff Law via Gcc-patches wrote:
>
> On 10/30/20 7:01 AM, Richard Biener wrote:
>>
>> It's not that more / different inlining inherently exposes _more_
>> false positives in the middle-end warnings. They simply expose
>> others and the GCC codebase is cleansed (by those who chan
On 10/30/20 7:01 AM, Richard Biener wrote:
>
> It's not that more / different inlining inherently exposes _more_
> false positives in the middle-end warnings. They simply expose
> others and the GCC codebase is cleansed (by those who change
> inliner heuristics / tunings) from those by either fi
On Fri, Oct 30, 2020 at 11:09 AM Stefan Schulze Frielinghaus via
Gcc-patches wrote:
>
> On Wed, Oct 28, 2020 at 11:34:53AM -0600, Jeff Law wrote:
> >
> > On 10/28/20 11:29 AM, Stefan Schulze Frielinghaus wrote:
> > > On Wed, Oct 28, 2020 at 08:39:41AM -0600, Jeff Law wrote:
> > >> On 10/28/20 3:38
On Wed, Oct 28, 2020 at 11:34:53AM -0600, Jeff Law wrote:
>
> On 10/28/20 11:29 AM, Stefan Schulze Frielinghaus wrote:
> > On Wed, Oct 28, 2020 at 08:39:41AM -0600, Jeff Law wrote:
> >> On 10/28/20 3:38 AM, Stefan Schulze Frielinghaus via Gcc-patches wrote:
> >>> On Mon, Oct 05, 2020 at 02:02:57PM
Jeff Law via Gcc-patches writes:
> On 10/28/20 11:29 AM, Stefan Schulze Frielinghaus wrote:
>> On Wed, Oct 28, 2020 at 08:39:41AM -0600, Jeff Law wrote:
>>> On 10/28/20 3:38 AM, Stefan Schulze Frielinghaus via Gcc-patches wrote:
On Mon, Oct 05, 2020 at 02:02:57PM +0200, Stefan Schulze Frielin
On 10/28/20 11:29 AM, Stefan Schulze Frielinghaus wrote:
> On Wed, Oct 28, 2020 at 08:39:41AM -0600, Jeff Law wrote:
>> On 10/28/20 3:38 AM, Stefan Schulze Frielinghaus via Gcc-patches wrote:
>>> On Mon, Oct 05, 2020 at 02:02:57PM +0200, Stefan Schulze Frielinghaus via
>>> Gcc-patches wrote:
>>>
On Wed, Oct 28, 2020 at 08:39:41AM -0600, Jeff Law wrote:
>
> On 10/28/20 3:38 AM, Stefan Schulze Frielinghaus via Gcc-patches wrote:
> > On Mon, Oct 05, 2020 at 02:02:57PM +0200, Stefan Schulze Frielinghaus via
> > Gcc-patches wrote:
> >> On Tue, Sep 22, 2020 at 02:59:30PM +0200, Andreas Krebbel
On 10/28/20 3:38 AM, Stefan Schulze Frielinghaus via Gcc-patches wrote:
> On Mon, Oct 05, 2020 at 02:02:57PM +0200, Stefan Schulze Frielinghaus via
> Gcc-patches wrote:
>> On Tue, Sep 22, 2020 at 02:59:30PM +0200, Andreas Krebbel wrote:
>>> On 15.09.20 17:02, Stefan Schulze Frielinghaus wrote:
>
On Mon, Oct 05, 2020 at 02:02:57PM +0200, Stefan Schulze Frielinghaus via
Gcc-patches wrote:
> On Tue, Sep 22, 2020 at 02:59:30PM +0200, Andreas Krebbel wrote:
> > On 15.09.20 17:02, Stefan Schulze Frielinghaus wrote:
> > > Over the last couple of months quite a few warnings about uninitialized
>
On Tue, Sep 22, 2020 at 02:59:30PM +0200, Andreas Krebbel wrote:
> On 15.09.20 17:02, Stefan Schulze Frielinghaus wrote:
> > Over the last couple of months quite a few warnings about uninitialized
> > variables were raised while building GCC. A reason why these warnings
> > show up on S/390 only i
On 15.09.20 17:02, Stefan Schulze Frielinghaus wrote:
> Over the last couple of months quite a few warnings about uninitialized
> variables were raised while building GCC. A reason why these warnings
> show up on S/390 only is due to the aggressive inlining settings here.
> Some of these warnings
Over the last couple of months quite a few warnings about uninitialized
variables were raised while building GCC. A reason why these warnings
show up on S/390 only is due to the aggressive inlining settings here.
Some of these warnings (2c832ffedf0, b776bdca932, 2786c0221b6,
1657178f59b) could be
13 matches
Mail list logo