On Tue, Jul 17, 2018 at 09:39:03AM +0100, Andrew Cooper wrote:
> On 17/07/2018 07:57, Jan Beulich wrote:
> On 16.07.18 at 18:56, wrote:
> >> On 16/07/18 17:46, Jan Beulich wrote:
> >>> For a reason that I can't explain, it is only the shim build that fails
> >>> for me with an older gcc due
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, July 18, 2018 5:39 PM
>
> >>> On 18.07.18 at 11:36, wrote:
> > On Mon, Jul 16, 2018 at 10:46:11AM -0600, Jan Beulich wrote:
> >> For a reason that I can't explain, it is only the shim build that fails
> >> for me with an older gcc
On Wed, Jul 18, 2018 at 03:39:20AM -0600, Jan Beulich wrote:
> >>> On 18.07.18 at 11:36, wrote:
> > On Mon, Jul 16, 2018 at 10:46:11AM -0600, Jan Beulich wrote:
> >> For a reason that I can't explain, it is only the shim build that fails
> >> for me with an older gcc due to the compiler not
>>> On 18.07.18 at 11:36, wrote:
> On Mon, Jul 16, 2018 at 10:46:11AM -0600, Jan Beulich wrote:
>> For a reason that I can't explain, it is only the shim build that fails
>> for me with an older gcc due to the compiler not recognizing that
>> apparently uninitialized variables aren't really
On Mon, Jul 16, 2018 at 10:46:11AM -0600, Jan Beulich wrote:
> For a reason that I can't explain, it is only the shim build that fails
> for me with an older gcc due to the compiler not recognizing that
> apparently uninitialized variables aren't really uninitialized. Pull out
> the assignments
>>> On 16.07.18 at 18:56, wrote:
> On 16/07/18 17:46, Jan Beulich wrote:
>> For a reason that I can't explain, it is only the shim build that fails
>> for me with an older gcc due to the compiler not recognizing that
>> apparently uninitialized variables aren't really uninitialized.
>
> The only
On 17/07/2018 07:57, Jan Beulich wrote:
On 16.07.18 at 18:56, wrote:
>> On 16/07/18 17:46, Jan Beulich wrote:
>>> For a reason that I can't explain, it is only the shim build that fails
>>> for me with an older gcc due to the compiler not recognizing that
>>> apparently uninitialized
>>> On 16.07.18 at 18:56, wrote:
> On 16/07/18 17:46, Jan Beulich wrote:
>> For a reason that I can't explain, it is only the shim build that fails
>> for me with an older gcc due to the compiler not recognizing that
>> apparently uninitialized variables aren't really uninitialized.
>
> The only
On 16/07/18 17:46, Jan Beulich wrote:
> For a reason that I can't explain, it is only the shim build that fails
> for me with an older gcc due to the compiler not recognizing that
> apparently uninitialized variables aren't really uninitialized.
The only thing that comes to mind is some
For a reason that I can't explain, it is only the shim build that fails
for me with an older gcc due to the compiler not recognizing that
apparently uninitialized variables aren't really uninitialized. Pull out
the assignments used by two of the three case blocks and make them
initializers of the
10 matches
Mail list logo