search for: g_merg

...egressions in correctness and performance will be a significant challenge. * Ensure that the overall design meets the needs of general targets, not being overly tuned to a specific implementation. Design work planned These are some design changes coming in the near to medium term future: * The G_MERGE and G_UNMERGE opcodes will be split into separate opcodes to handle different use cases. At the moment the opcode is too powerful, resulting in overly complex handling in places like the legalizer. G_MERGE will be split so that it only handles merging of scalars into one larger scalar. For other c...

...nge. >> * Ensure that the overall design meets the needs of general targets, not >> being overly tuned to a specific implementation. >> >> Design work planned >> >> These are some design changes coming in the near to medium term future: >> >> * The G_MERGE and G_UNMERGE opcodes will be split into separate opcodes to >> handle different use cases. At the moment the opcode is too powerful, >> resulting in overly complex handling in places like the legalizer. G_MERGE >> will be split so that it only handles merging of scalars into one...

...nge. >> * Ensure that the overall design meets the needs of general targets, not >> being overly tuned to a specific implementation. >> >> Design work planned >> >> These are some design changes coming in the near to medium term future: >> >> * The G_MERGE and G_UNMERGE opcodes will be split into separate opcodes to >> handle different use cases. At the moment the opcode is too powerful, >> resulting in overly complex handling in places like the legalizer. G_MERGE >> will be split so that it only handles merging of scalars into one...

Hi, I’m trying to handle some vector operations with splitting/scalarization and keep running into similar sorts of issues which are making me question the intended function of the various legalization operations (particularly G_MERGE_VALUES/G_UNMERGE_VALUES, but also G_EXTRACT/G_INSERT and conversion instructions) and what the contract between the legalizer and selector actually is. For scalar values, things seem clearer, but I’m still confused. The AArch64 selector code seems content to allow strange sized values in the sour...