Re: Re[2]: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Vadim Zeitlin <vz-gcc@xxxxxxxxxxxx>
Subject: Re: Re[2]: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
Date: Fri, 23 Mar 2018 18:18:33 +0000
Cc: gcc-help <gcc-help@xxxxxxxxxxx>
In-reply-to: <E1ezREh-00028j-Fv@smtp.tt-solutions.com>
References: <E1ezQmN-000162-Sn@smtp.tt-solutions.com> <CAH6eHdT3Oaf5cTwp6fj=zfF3equwFC=pVtvgbxoK0WF1s7SnzQ@mail.gmail.com> <E1ezREh-00028j-Fv@smtp.tt-solutions.com>

On 23 March 2018 at 18:16, Vadim Zeitlin wrote:
>  Just to be clear, this is what bothers me the most: how can these warnings
> options affect the optimizer output? Shouldn't this be "impossible"?

Yes, they should have no effect on the generated code.

Follow-Ups:
- Re[4]: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
  - From: Vadim Zeitlin

References:
- Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
  - From: Vadim Zeitlin
- Re: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
  - From: Jonathan Wakely
- Re[2]: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
  - From: Vadim Zeitlin

Prev by Date: Re[2]: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
Next by Date: Re[4]: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
Previous by thread: Re[2]: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
Next by thread: Re[4]: Using -Wall and -Woverloaded-virtual together changes the behaviour of the code
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]