On 07/23/2018 02:18 AM, Jakub Jelinek wrote:
On Sun, Jul 22, 2018 at 04:43:17PM -0600, Martin Sebor wrote:
OK with the nit fixed. IF you need to update the doc changes as a
result of the -faligned-* changes, those are pre-approved.
I had to adjust a few more tests and make a couple of minor
On Sun, Jul 22, 2018 at 04:43:17PM -0600, Martin Sebor wrote:
> > > > OK with the nit fixed. IF you need to update the doc changes as a
> > > > result of the -faligned-* changes, those are pre-approved.
> > >
> > >
> > > I had to adjust a few more tests and make a couple of minor
> > > tweaks as
On 07/21/2018 06:42 PM, H.J. Lu wrote:
On Fri, Jul 20, 2018 at 1:57 PM, Martin Sebor wrote:
On 07/19/2018 04:31 PM, Jeff Law wrote:
On 06/24/2018 03:05 PM, Martin Sebor wrote:
Storing integer command line option arguments in type int
limits options such as -Wlarger-than= or -Walloca-larger-
On Fri, Jul 20, 2018 at 1:57 PM, Martin Sebor wrote:
> On 07/19/2018 04:31 PM, Jeff Law wrote:
>>
>> On 06/24/2018 03:05 PM, Martin Sebor wrote:
>>>
>>> Storing integer command line option arguments in type int
>>> limits options such as -Wlarger-than= or -Walloca-larger-than
>>> to at most INT_MA
On 07/19/2018 04:31 PM, Jeff Law wrote:
On 06/24/2018 03:05 PM, Martin Sebor wrote:
Storing integer command line option arguments in type int
limits options such as -Wlarger-than= or -Walloca-larger-than
to at most INT_MAX (see bug 71905). Larger values wrap around
zero. The value zero is cons
On 06/24/2018 03:05 PM, Martin Sebor wrote:
> Storing integer command line option arguments in type int
> limits options such as -Wlarger-than= or -Walloca-larger-than
> to at most INT_MAX (see bug 71905). Larger values wrap around
> zero. The value zero is considered to disable the option,
> mak
