search for: ms_struct

...ome/jay/git/llvm/projects/test-suite/include -I../../include -I/home/jay/llvm/gitobjdir/include -I/home/jay/git/llvm/include -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -DNDEBUG -O3 -mllvm -disable-llvm-optzns -m64 -fomit-frame-pointer -S /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c -o Output/ms_struct-bitfield-init-1.ll -emit-llvm /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c:28: error: size of array ‘a3’ is negative make[3]: [Output/ms_struct-bitfield-init-1.ll] Error 1 (ignored) /home/jay/llvm/gitobjdir/Rele...

...jects/test-suite/include -I../../include > -I/home/jay/llvm/gitobjdir/include -I/home/jay/git/llvm/include > -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -DNDEBUG  -O3 -mllvm > -disable-llvm-optzns  -m64 -fomit-frame-pointer -S > /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c > -o Output/ms_struct-bitfield-init-1.ll -emit-llvm > /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c:28: > error: size of array ‘a3’ is negative If I compile this test by hand, I get the same error: $ llvm-gcc -c ms_struct...

.../include -I../../include >> -I/home/jay/llvm/gitobjdir/include -I/home/jay/git/llvm/include >> -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -DNDEBUG  -O3 -mllvm >> -disable-llvm-optzns  -m64 -fomit-frame-pointer -S >> /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c >> -o Output/ms_struct-bitfield-init-1.ll -emit-llvm >> /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c:28: >> error: size of array ‘a3’ is negative > > If I compile this test by hand, I get the same error: &gt...

...jects/test-suite/include -I../../include > -I/home/jay/llvm/gitobjdir/include -I/home/jay/git/llvm/include > -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -DNDEBUG -O3 -mllvm > -disable-llvm-optzns -m64 -fomit-frame-pointer -S > /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c > -o Output/ms_struct-bitfield-init-1.ll -emit-llvm > /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c:28: > error: size of array ‘a3’ is negative > make[3]: [Output/ms_struct-bitfield-init-1.ll] Error 1 (ignored) > /hom...

On May 6, 2011, at 1:29 AM, Jay Foad wrote: > This seems wrong -- if a test fails, it shouldn't stop the whole > "make", it should just get logged as a failure and continue. That's a frustrating aspect of the test-suite Makefiles. I don't know how to work around it without removing the test from your tree. -Andy

On May 6, 2011, at 4:57 PM, Andrew Trick wrote: > On May 6, 2011, at 1:29 AM, Jay Foad wrote: > >> This seems wrong -- if a test fails, it shouldn't stop the whole >> "make", it should just get logged as a failure and continue. > > That's a frustrating aspect of the test-suite Makefiles. I don't know how to work around it without removing the test

Fariborz, On May 6, 2011, at 5:07 PM, Fariborz Jahanian wrote: > > On May 6, 2011, at 4:57 PM, Andrew Trick wrote: > >> On May 6, 2011, at 1:29 AM, Jay Foad wrote: >> >>> This seems wrong -- if a test fails, it shouldn't stop the whole >>> "make", it should just get logged as a failure and continue. >> >> That's a

> So how about the attached patch? OK to commit? Or here's a different way of patching it, if you prefer. Thanks, Jay. -------------- next part -------------- A non-text attachment was scrubbed... Name: pragma-ms-struct-2 Type: application/octet-stream Size: 989 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110615/a1ebe3af/attachment.obj>

...ingleSource/UnitTests/Vector/sumarray-dbl SingleSource/UnitTests/vla SingleSource/UnitTests/Vector/Altivec/2007-01-07-lvsl-lvsr-Regression SingleSource/UnitTests/Vector/Altivec/alti.sdot SingleSource/UnitTests/Vector/Altivec/casts SingleSource/UnitTests/Vector/Altivec/test1 SingleSource/UnitTests/ms_struct-bitfield SingleSource/UnitTests/ms_struct-bitfield-1 SingleSource/UnitTests/ms_struct-bitfield-init SingleSource/UnitTests/ms_struct-bitfield-init-1 SingleSource/UnitTests/ms_struct_pack_layout SingleSource/UnitTests/ms_struct_pack_layout-1 If anyone has any proposed modifications to this list, pl...

More MSVC compatibility fixes, for packed structures. NB: In case you are aware of the issues that may come with MS vs GCC packing, so far, I have not seen evidence of detrimental impact from using ms_struct packing in MSVC (vs gcc_struct, which is explicitly specified for MinGW), with regards to the sections of code I am using in Rufus. -------------- next part --------------

Can anyone shed some light on the origins of the comments... /* Mach-O doesn't support omitting the frame pointer for now. */ ...in gcc/config/i386/i386.c. FSF gcc trunk has enabled the omit-frame-pointer option as the default for both i386 and x86_64 recently. * config.gcc: Handle --enable-frame-pointer. * configure.ac: Add --enable-frame-pointer. * configure: Regenerated. *

...4, 2016 at 8:02 AM, Pete Batard via Syslinux <syslinux at zytor.com> wrote: > More MSVC compatibility fixes, for packed structures. > NB: In case you are aware of the issues that may come with MS vs GCC > packing, so far, I have not seen evidence of detrimental impact from using > ms_struct packing in MSVC (vs gcc_struct, which is explicitly specified for > MinGW), with regards to the sections of code I am using in Rufus. > > From 13b39c1f113a8bc5621249db21a382a689aa174e Mon Sep 17 00:00:00 2001 > From: Pete Batard <pete at akeo.ie> > Date: Tue, 23 Feb 2016 19:57:...

...code mode, which is what Rufus uses with MSVC. o [PATCH 3/5] installers: MSVC compatibility fixes More MSVC compatibility fixes, for packed structures. NB: In case you are aware of the issues that may come with MS vs GCC packing, so far, I have not seen evidence of detrimental impact from using ms_struct packing in MSVC (vs gcc_struct, which is explicitly specified for MinGW), with regards to the sections of code I am using in Rufus. o [PATCH 4/5] installers: fix a possible buffer overflow when looking for LDLINUX_MAGIC If the ldlinux being processed is garbage, the search for LDLINUX_MAGIC wi...

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability

...13277 mpeg2dec.ll 12 68101 0 0.02 68066 0 0.02 68066 mpglib_main.ll 5 28228 0 0.00 28197 0 0.01 28197 mpistubs.ll 45 34470 16 0.01 28963 9 0.01 29751 MSalign11.ll 5 115701 0 0.02 115686 0 0.02 115686 MSalignmm.ll 5 185410 0 0.03 185395 0 0.02 185395 mshortest.ll 3 106701 0 0.01 106668 0 0.02 106668 ms_struct-bitfield-1.ll 1 2844 0 0.01 2835 0 0.01 2835 ms_struct-bitfield-init-1.ll 1 9535 0 0.01 9526 0 0.01 9526 ms_struct-bitfield-init.ll 1 5713 0 0.01 5704 0 0.01 5704 ms_struct-bitfield.ll 1 2461 0 0.01 2452 0 0.01 2452 ms_struct_pack_layout-1.ll 1 822 0 0.01 813 0 0.01 813 ms_struct_pack_layout.ll 1 1...