On Sat, Jan 26, 2019 at 1:04 PM Martin Jansa wrote:
>
> > 2. Just use -mcpu and do not use -march/-mtune and may be provide
> > mechanism to override -mcpu, which is done by packages anyway ( maps
> > directly to package architectures )
>
> This would be my preferred solution, I know that tune
> 2. Just use -mcpu and do not use -march/-mtune and may be
provide mechanism to override -mcpu, which is done by packages anyway (
maps directly to package architectures )
This would be my preferred solution, I know that tune files are already
quite complicated, but another variable which will
On Sat, Jan 26, 2019 at 9:39 AM Martin Jansa wrote:
>
> Which -mcpu/-march combination is causing issue in gcc9?
Its when using cortex-a5 tunes, -march=armv7-a -mcpu=cortex-a5, but if
we move the needle to fix the issue or test coverage then we miss the
point here, the fact that this keeps
Which -mcpu/-march combination is causing issue in gcc9?
I know we had this issue with armv7a tunes before, that's why I've added
separate armv7ve before the switch from -mtune to -mcpu.
I still believe -mcpu (with or without -march) is better option.
Using -mtune without indicating which
On Fri, Jan 25, 2019 at 12:32 PM Mark Hatle
wrote:
>
> On 1/24/19 9:22 PM, Khem Raj wrote:
> > On Wed, Jan 23, 2019 at 6:11 PM Andre McCurdy
wrote:
> >>
> >> On Wed, Jan 23, 2019 at 2:50 PM Khem Raj wrote:
> >>>
> >>> On Wed, Jan 23, 2019 at 5:27 PM Andre McCurdy
wrote:
>
> On Wed,
On Thu, 2019-01-24 at 22:22 -0500, Khem Raj wrote:
> On Wed, Jan 23, 2019 at 6:11 PM Andre McCurdy
> wrote:
> > On Wed, Jan 23, 2019 at 2:50 PM Khem Raj
> > wrote:
> > > On Wed, Jan 23, 2019 at 5:27 PM Andre McCurdy <
> > > armccu...@gmail.com> wrote:
> > > > On Wed, Jan 23, 2019 at 12:05 PM
On 1/24/19 9:22 PM, Khem Raj wrote:
> On Wed, Jan 23, 2019 at 6:11 PM Andre McCurdy wrote:
>>
>> On Wed, Jan 23, 2019 at 2:50 PM Khem Raj wrote:
>>>
>>> On Wed, Jan 23, 2019 at 5:27 PM Andre McCurdy wrote:
On Wed, Jan 23, 2019 at 12:05 PM Khem Raj wrote:
>
> tune files which
On Wed, Jan 23, 2019 at 6:11 PM Andre McCurdy wrote:
>
> On Wed, Jan 23, 2019 at 2:50 PM Khem Raj wrote:
> >
> > On Wed, Jan 23, 2019 at 5:27 PM Andre McCurdy wrote:
> > >
> > > On Wed, Jan 23, 2019 at 12:05 PM Khem Raj wrote:
> > > >
> > > > tune files which inherit the arch definitions
On Wed, Jan 23, 2019 at 2:50 PM Khem Raj wrote:
>
> On Wed, Jan 23, 2019 at 5:27 PM Andre McCurdy wrote:
> >
> > On Wed, Jan 23, 2019 at 12:05 PM Khem Raj wrote:
> > >
> > > tune files which inherit the arch definitions already define appropriate
> > > -mcpu option, which is equivalent of right
On Wed, Jan 23, 2019 at 5:27 PM Andre McCurdy wrote:
>
> On Wed, Jan 23, 2019 at 12:05 PM Khem Raj wrote:
> >
> > tune files which inherit the arch definitions already define appropriate
> > -mcpu option, which is equivalent of right -march and -mtune combination
>
> And what about machines
On Wed, Jan 23, 2019 at 12:05 PM Khem Raj wrote:
>
> tune files which inherit the arch definitions already define appropriate
> -mcpu option, which is equivalent of right -march and -mtune combination
And what about machines which inherit an arch definition instead of a
cpu definition? Is that
tune files which inherit the arch definitions already define appropriate
-mcpu option, which is equivalent of right -march and -mtune combination
and is preferred since gcc is getting stricter and stricter with option
check semantics and can now find incompatible -march and -mcpu options
better
12 matches
Mail list logo