On Tue, Jun 12, 2012 at 10:22 AM, Mike Stump wrote:
> On Jun 11, 2012, at 7:41 PM, Janis Johnson wrote:
>> The tests in gcc.dg/torture/stackalign use two sets of torture options:
>
>> OK for mainline?
>
> Ok, if H.J. is happy.
It is OK for me. Thanks.
--
H.J.
On Jun 11, 2012, at 7:41 PM, Janis Johnson wrote:
> The tests in gcc.dg/torture/stackalign use two sets of torture options:
> OK for mainline?
Ok, if H.J. is happy.
On Tue, Jun 12, 2012 at 7:59 AM, Janis Johnson wrote:
> On 06/11/2012 09:05 PM, H.J. Lu wrote:
>> On Mon, Jun 11, 2012 at 7:41 PM, Janis Johnson
>> wrote:
>>> The tests in gcc.dg/torture/stackalign use two sets of torture options:
>>> the usual optimization sets used as default for torture tests
On 06/11/2012 09:05 PM, H.J. Lu wrote:
> On Mon, Jun 11, 2012 at 7:41 PM, Janis Johnson
> wrote:
>> The tests in gcc.dg/torture/stackalign use two sets of torture options:
>> the usual optimization sets used as default for torture tests, and up to
>> four sets of options that are specific to stac
On Mon, Jun 11, 2012 at 7:41 PM, Janis Johnson wrote:
> The tests in gcc.dg/torture/stackalign use two sets of torture options:
> the usual optimization sets used as default for torture tests, and up to
> four sets of options that are specific to stack alignment. Currently
> the stack alignment o
The tests in gcc.dg/torture/stackalign use two sets of torture options:
the usual optimization sets used as default for torture tests, and up to
four sets of options that are specific to stack alignment. Currently
the stack alignment options are passed via an option that is used by the
dg-test opt
