similar to: __auto_type doesn't warn when a pointer is used as a declarator

Hi All , Was going through the C99 standard @ http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf which states that the Function declarators as direct-declarator ( parameter-type-list ) parameter-list: parameter-declaration parameter-list , parameter-declaration parameter-declaration: declaration-specifiers declarator

What fun. I don't often stoke up the boiler and actually compile open-source code, but here I am at the beginning of just such a joyous and wondrous adventure. I'm running the latest level of AIX (V5.3...V4.3 has been obsolete for at least, what, 5 years) and using the IBM compiler (xlc is similarly obsolete, from back when the compiler came with the O/S...oh, for the halcyon days of

On Tue, Jun 30, 2020 at 7:39 PM Will Deacon <will at kernel.org> wrote: > +#define __READ_ONCE(x) \ > +({ \ > + int atomic = 1; \ > + union { __unqual_scalar_typeof(x) __val; char __c[1]; } __u; \ > +

On Tue, Jun 30, 2020 at 7:39 PM Will Deacon <will at kernel.org> wrote: > +#define __READ_ONCE(x) \ > +({ \ > + int atomic = 1; \ > + union { __unqual_scalar_typeof(x) __val; char __c[1]; } __u; \ > +

On 30 Jun 2016, at 17:26, Odhiambo Washington <odhiambo at gmail.com> wrote: > > FreeBSD 9.3-STABLE FreeBSD 9.3-STABLE amd64: > > sha1.h:80: error: static or type qualifiers in abstract declarator What gcc version is this? It should have been valid C99 code, so I expected it to work without any special version checks..

For the following code: struct XBeePacket; typedef void (*CompletionProc)(XBeePacket* inPacket, void* inParam2); struct XBeePacket { bool mField1; CompletionProc mCompletionProc; }; Why does clang emit this IR? %struct.XBeePacket = type { i8, {}* } define void @MyCompletionProc(%struct.XBeePacket* %inPacket, i8*

Status: We have a 3 node gluster cluster (proxmox based) - gluster 3.8.12 - Replica 3 - VM Hosting Only - Sharded Storage Or I should say we *had* a 3 node cluster, one node died today. Possibly I can recover it, in whcih case no issues, we just let it heal itself. For now its running happily on 2 nodes with no data loss - gluster for teh win! But its looking like I might have to replace the

Tried to update from 2.2.24 to 2.2.25 using same configure command as previously. make ends with: In file included from guid.c:6: sha1.h:80: error: static or type qualifiers in abstract declarator make[4]: *** [guid.lo] Error 1 make[3]: *** [all] Error 2 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Mac OS X 10.7.5 Configure statement was:

> And a big thanks (*not*) to the smart reporting which showed no issues at > all. Heh, on that, did you think to take a look at the Media_Wearout indicator ? I recently learned that existed, and it explained A LOT. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Digital signature URL:

Hi Rick, this is a bug in Clang's LLVM-IR code generator: http://llvm.org/bugs/show_bug.cgi?id=14920 Best, Florian On Sunday, January 20, 2013 01:57:37 Rick Mann wrote: > For the following code: > > struct XBeePacket; > > typedef void (*CompletionProc)(XBeePacket* inPacket, void* inParam2); > > struct > XBeePacket > { >

The preferred implementation uses __auto_type, a GCC extension also now supported by Clang. Unfortunately OpenBSD ships with GCC 4.2.1 (from 2007!) which predates this extension by quite a few years, so we have to be able to fall back to a plain macro. --- configure.ac | 20 ++++++++++- common/include/minmax.h | 63 +++++++++++++++++++++++++++++++++++

The preferred implementation uses __auto_type, a GCC extension also now supported by Clang. Unfortunately OpenBSD ships with GCC 4.2.1 (from 2007!) which predates this extension by quite a few years, so we have to be able to fall back to a plain macro. --- configure.ac | 20 ++++++++++- common/include/minmax.h | 63 +++++++++++++++++++++++++++++++++++

Yet another newbie question here. My setup is thus: I have lighty running with scgi (working fine) on windows XP sp 2. Rails 1.1 and ruby 1.8.x. The server and scgi are working. I know this because I can get a test page to work easily enough. I did the following: ruby script\generate model Recipe [following the Rolling with Rails Tutorial] ruby script\generate controller Recipe I also

Hello, I am tying to compile Dovecot 2.2.27 on Solaris 10, and I get this error: test-ioloop.c: In function `test_ioloop_pending_io': test-ioloop.c:188: error: size of array `type name' is negative My configuration is like this: Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : poll I/O notifys .... : none SSL ............ : yes (OpenSSL) GSSAPI ......... : no

Hi, Suppose I have a pointer to "something" (a structure I defined) and I want to pass the pointer to a generic function, that gets a 64-bit address pointer. How do I do that? For instance: The function is: void Foo (void *); I get the specific pointer using getPointerOperand() on a store instruction that store to it: inst->getPointerOperand()->getType() Now I want

On 01 Jul 2016, at 19:09, Juan C. Blanco <jcblanco at fi.upm.es> wrote: > > I Haven't had the time to check the sha1.h error with the new fixes but I've just done so after de 2.2.25 release was out and I'm having the same error: > > gcc -DHAVE_CONFIG_H -I. -I. -I../.. -std=gnu99 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector

I've always wondered how the in-line sizes of SmallVector, SmallString, etc. that we use in LLVM and Clang hold up against the actual sizes of the containers at run-time. To figure this out, I added a destructor to each such class, that would dump the container's final size into a table that got printed at exit. I also added a special field, __clang_ObjectLocation, to each such class and

Hi,, In src/lib/mountpoint.c:53 the following had to be commented out: // point_r->type = p_strdup(pool, buf.f_fstypename); because f_fstypename is undeclared on this OS. Also the following errors occur with the DEC C compiler (which compiles the other files just fine): source='file-cache.c' object='file-cache.o' libtool=no DEPDIR=.deps depmode=none

Hello. I cant build 2.2.25, but I can build fine version 2.2.24 with same options: RedHat based customized distro, 2.6.28.10 kernel Build options: export CPPFLAGS export LDFLAGS CPPFLAGS=-I/usr/local/ssl/include LDFLAGS=-L/usr/local/ssl/lib ./configure \ --prefix=/usr \ --with-ssl=openssl \ --with-ssldir=/etc/ssl \ --sysconfdir=/etc \

Can we go back a little? 1) Add a new transformation to InstCombine that will replace 'getelementptr > i8, i8* null, <ty> %n' with 'inttoptr <ty> %n to i8*' when <ty> has the > same size as a pointer for the target architecture. What's the actual problem with this approach? I personally find it the most compelling - it is well-defined (well,