Please take your personal political agenda to private email. This is a mailing
list, not your soap box. Saying that I’m unsubscribing and using Linux or
geonode as my ai platform.
Sent from my iPhone
> On Jul 8, 2019, at 2:53 PM, Jonathan Wakely wrote:
>
>
>
>> On Mon, 8 Jul 2019 at 21:44,
On Mon, 8 Jul 2019 at 21:44, Unidef wrote:
> I’m really sorry, I have a medical condition heh
>
> But I meant multidimensional functions
>
This is still the wrong mailing list though.
I’m really sorry, I have a medical condition heh
But I meant multidimensional functions
I think I can do it with pointer function arrays, but let’s say I have a multi
dimensional multi directional binary tree (graph) and I set it to a _all struct
I want to do
secure _all[200][macro] /* etc */
On Mon, 8 Jul 2019 at 14:53, Unidef wrote:
>
> Is it possible to have c or c++ natively have multi dimensional arrays?
> Instead of using some bourgeois macro function?
This doesn't seem like a question about GCC development, so is
off-topic on this mailing list.
If you want to know if it's pos
Is it possible to have c or c++ natively have multi dimensional arrays? Instead
of using some bourgeois macro function?
Sent from my iPhone
On 6/21/19 4:28 PM, Richard Biener wrote:
> On Fri, Jun 21, 2019 at 4:13 PM Jakub Jelinek wrote:
>>
>> On Fri, Jun 21, 2019 at 04:04:00PM +0200, Martin Liška wrote:
>>> On 6/21/19 1:58 PM, Jakub Jelinek wrote:
On Fri, Jun 21, 2019 at 01:52:09PM +0200, Martin Liška wrote:
> On 6/21/19 1:47
On Sun, Jul 7, 2019 at 8:40 AM Thomas Womack wrote:
>
> Good morning.
>
> I have some code that looks like
>
> typedef unsigned long long uint64;
> typedef unsigned int uint32;
>
> typedef struct { uint64 x[8]; } __attribute__((aligned(64))) v_t;
>
> inline v_t xor(v_t a, v_t b)
> {
> v_t Q;
>
On Mon, 8 Jul 2019 at 11:33, wrote:
>
> There was recently a discussion with confusion regarding initialization
> with {} instead of {0} when initializing an empty array or struct. The
> former is not valid in C, but GCC permits it anyway even though it's not
> explained anywhere in the specs:
> c
There was recently a discussion with confusion regarding initialization
with {} instead of {0} when initializing an empty array or struct. The
former is not valid in C, but GCC permits it anyway even though it's not
explained anywhere in the specs:
char something[20] = {};
Is it missing from t
