On Sat, 2023-09-09 at 14:26 +0800, Yang Yujie wrote:
> I remember you were against it because you think non-multilib users
> would be punished because the libdir layout changes (no toplevel).
> However this directory should be (mostly) private to each gcc instance,
> so I don't see real consequence
On Sat, Sep 09, 2023 at 01:56:57PM +0800, Xi Ruoyao wrote:
> On Sat, 2023-09-09 at 10:46 +0800, Yang Yujie wrote:
> > The next option I can think of would be MULTILIB_EXTRA_OPTS, where
> > -fmultiflags
> > fit in nicely. However, these options won't reach the toplevel builds, and
> > tweaking con
On Sat, 2023-09-09 at 10:46 +0800, Yang Yujie wrote:
> The next option I can think of would be MULTILIB_EXTRA_OPTS, where
> -fmultiflags
> fit in nicely. However, these options won't reach the toplevel builds, and
> tweaking config-ml.in for getting it there would be quite tedious and perhaps
> u
On Thu, Sep 07, 2023 at 07:54:41PM +0800, Yang Yujie wrote:
> On Thu, Sep 07, 2023 at 05:47:36PM +0800, Xi Ruoyao wrote:
> > On Thu, 2023-09-07 at 17:31 +0800, Yang Yujie wrote:
> > > > This is bad. It makes BOOT_CFLAGS=-mlasx or CFLAGS_FOR_TARGET=-mlasx
> > > > silently ignored so we cannot test
On Thu, Sep 07, 2023 at 05:47:36PM +0800, Xi Ruoyao wrote:
> On Thu, 2023-09-07 at 17:31 +0800, Yang Yujie wrote:
> > > This is bad. It makes BOOT_CFLAGS=-mlasx or CFLAGS_FOR_TARGET=-mlasx
> > > silently ignored so we cannot test a LSX/LASX or vectorizer change with
> > > them.
> > >
> > > Why do
On Thu, 2023-09-07 at 17:47 +0800, Xi Ruoyao wrote:
/* snip */
> I've made some local experiment too, I think we can add a "-mbuild-
> multilib" option which does nothing but in the hacked spec we can wrap
> the line in %{mbuild-multilib:...}:
>
> %{mbuild-multilib:% %{mabi=lp64d:-march=la464 -m
On Thu, 2023-09-07 at 17:31 +0800, Yang Yujie wrote:
> > This is bad. It makes BOOT_CFLAGS=-mlasx or CFLAGS_FOR_TARGET=-mlasx
> > silently ignored so we cannot test a LSX/LASX or vectorizer change with
> > them.
> >
> > Why do we need to purge all user-specified -m options here?
>
> Yes, that is
> This is bad. It makes BOOT_CFLAGS=-mlasx or CFLAGS_FOR_TARGET=-mlasx
> silently ignored so we cannot test a LSX/LASX or vectorizer change with
> them.
>
> Why do we need to purge all user-specified -m options here?
Yes, that is an issue that I haven't considered.
The purge rules (self_specs) e
On Wed, 2023-09-06 at 09:04 +0800, Yang Yujie wrote:
> On Tue, Sep 05, 2023 at 09:31:56PM +0800, Xi Ruoyao wrote:
> > On Thu, 2023-08-31 at 20:48 +0800, Yang Yujie wrote:
> > > * Support options for LoongArch SIMD extensions:
> > > new configure options --with-simd={none,lsx,lasx};
> > > new co
On Tue, Sep 05, 2023 at 09:31:56PM +0800, Xi Ruoyao wrote:
> On Thu, 2023-08-31 at 20:48 +0800, Yang Yujie wrote:
> > * Support options for LoongArch SIMD extensions:
> > new configure options --with-simd={none,lsx,lasx};
> > new compiler option -msimd={none,lsx,lasx};
> > new driver options
On Thu, 2023-08-31 at 20:48 +0800, Yang Yujie wrote:
> * Support options for LoongArch SIMD extensions:
> new configure options --with-simd={none,lsx,lasx};
> new compiler option -msimd={none,lsx,lasx};
> new driver options -m[no]-l[a]sx.
Hmm... In my build (a cross compiler configured with
在 2023/9/5 下午8:17, Xi Ruoyao 写道:
On Tue, 2023-09-05 at 20:01 +0800, chenglulu wrote:
在 2023/9/5 下午7:51, Xi Ruoyao 写道:
On Thu, 2023-08-31 at 20:48 +0800, Yang Yujie wrote:
/* Note: optimize_size may vary across functions,
while -m[no]-memcpy imposes a global constraint. */
#defin
On Tue, 2023-09-05 at 20:01 +0800, chenglulu wrote:
>
> 在 2023/9/5 下午7:51, Xi Ruoyao 写道:
> > On Thu, 2023-08-31 at 20:48 +0800, Yang Yujie wrote:
> > > /* Note: optimize_size may vary across functions,
> > > while -m[no]-memcpy imposes a global constraint. */
> > > #define TARGET_DO_OPTI
在 2023/9/5 下午7:51, Xi Ruoyao 写道:
On Thu, 2023-08-31 at 20:48 +0800, Yang Yujie wrote:
/* Note: optimize_size may vary across functions,
while -m[no]-memcpy imposes a global constraint. */
#define TARGET_DO_OPTIMIZE_BLOCK_MOVE_P
loongarch_do_optimize_block_move_p()
-#ifndef HAVE_AS
On Thu, 2023-08-31 at 20:48 +0800, Yang Yujie wrote:
> /* Note: optimize_size may vary across functions,
> while -m[no]-memcpy imposes a global constraint. */
> #define TARGET_DO_OPTIMIZE_BLOCK_MOVE_P
> loongarch_do_optimize_block_move_p()
>
> -#ifndef HAVE_AS_EXPLICIT_RELOCS
> -#define H
15 matches
Mail list logo
