Last year I posted a series of patches that added the concept of
"sizeless" types to the C and C++ frontends, in order to support
the SVE vector and predicate types:
https://gcc.gnu.org/ml/gcc-patches/2018-10/msg00868.html
That thread generated a lot of useful discussion and feedback, thanks.
T
Hi,
I wanted to check if you'd be interested in purchasing updated MATLAB Users
List for your sales and marketing initiatives?
Some users list you might be interested : Microstrategy, Splunk Enterprise,
COMSOL Multiphysics, Zoho, Qubole, Fusion 360 and many more.
If you are interested l
Hello gcc developers!
I am working on a new back end for my MRISC32 ISA [1], and I'm still very
new to gcc internals. I suspect that I will have more questions further
down the road, but let's start with this topic...
The MRISC32 ISA has instructions for setting a register based on the
outcome o
On 11/12/19 11:29 AM, m wrote:
> Hello gcc developers!
>
> I am working on a new back end for my MRISC32 ISA [1], and I'm still very
> new to gcc internals. I suspect that I will have more questions further
> down the road, but let's start with this topic...
>
> The MRISC32 ISA has instructions f
On Tue, Nov 12, 2019 at 8:06 AM Richard Sandiford
wrote:
> If the use of sizeless types does expand beyond SVE built-in types
> in future, the places that call the hook are the places that would
> need to deal directly with sizeless types.
We are using the same sizeless type infrastructure for th
Den 2019-11-12 kl. 19:54, skrev Jeff Law:
On 11/12/19 11:29 AM, m wrote:
Hello gcc developers!
I am working on a new back end for my MRISC32 ISA [1], and I'm still very
new to gcc internals. I suspect that I will have more questions further
down the road, but let's start with this topic...
The
Hi Jim,
Jim Wilson writes:
> On Tue, Nov 12, 2019 at 8:06 AM Richard Sandiford
> wrote:
>> If the use of sizeless types does expand beyond SVE built-in types
>> in future, the places that call the hook are the places that would
>> need to deal directly with sizeless types.
>
> We are using the s
