> From: Kumar, Venkataramanan <[email protected]> > Sent: Tuesday, June 30, 2026 2:43 PM > > > > > > From: Dipesh Sharma <[email protected]> > > > Sent: Friday, June 26, 2026 8:16 PM > > > > I don't get the intuition of the patch. Could you explain it more for why do > we > > need a brand new -mtile? It does not introduce anything. If you just want to > > share the intrins and builtins, we don't need to introduce -mtile. You could > > refer to how we handle VNNI. > > > Just to summarize, both ACE and AMX supports these tile management > Instructions. > > TILEZERO > LDTILECFG > STTILECFG > TILERELEASE > > AMX has these additional ones. > TILELOADD > TILELOADDT1 > TILESTORED > > -mtile was added to separate out common ones and share the intrinsics. > > > And I suppose this worth discussion. Since legacy AMX and ACE could not > me > > used together, should we share intrins? > Do you want to keep new intrinsic names for ace tile management > instructions?? > > > Builtins should be shared since for compiler they are the same. Using > different > > intrins could remind users they are different. > > Our understanding was that if we specify OPTION_MASK_ISA2_AMX_TILE | > OPTION_MASK_ISA2_ACEV1, then we need to specify both -mace-v1 and - > mamx-tile in order to enable this builtin . > DESC (OPTION_MASK_ISA_64BIT, OPTION_MASK_ISA2_AMX_TILE, > CODE_FOR_nothing, "__builtin_ia32_ldtilecfg", IX86_BUILTIN_LDTILECFG, > UNKNOWN, (int) VOID_FTYPE_PCVOID) > > We added OPTION_MASK_ISA2_TILE new mask which will be set when either > -mamx-tile or -mace-v1 is given. > Is there better way to do this ?? Looking at how the VNNI ones are done. >
You could use SHARE_BUILTIN in i386-expand.cc to override this logic. It will transfer it from "and" to "or". Thx, Haochen
