search for: funsigned

When I try to compile the menu I got the following: gcc -m32 -funsigned-char -g -W -Wall -march=i386 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -Os -MMD -S -o main.s main.c echo '.code16gcc' | cat - main.s > main.s16 as -o main.o16 main.s16 gcc -m32 -funsigned-char -g -W -Wall -march=i386 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -Os -MMD...

...e >= 128. > > I'd rather that they not be treated specially. If char defaulted to > unsigned char, there would be little reason to create this special case. I don't understand what you're getting at here. You can change char to default to unsigned right now with llvm-gcc -funsigned-char. I don't understand how that would change anything to be more useful though. > >This is a very interesting idea, particularly for languages like C++ that > >have a ton of types. Before making this change, I would want to see some > >numbers though. In particular, I do...

On Fri, 2004-08-20 at 18:43, Chris Lattner wrote: > I don't understand what you're getting at here. You can change char to > default to unsigned right now with llvm-gcc -funsigned-char. I don't > understand how that would change anything to be more useful though. The only thing it would change is that character constants with values > 63 would get encoded in 1 byte instead of 2 (with current implementation). I'm making a change that will ALWAYS encode UByteTy...

...cc" and then getting an x86_64 assembler instead of the MIPS cross-assembler. Adding a -v flag seems to confirm this thinking. With "-ccc-host-triple mips-sde-elf" and the -v flag, I get this invocation to the assembler (-D, -W and -I flags removed): "/usr/bin/gcc" -funsigned-char -msoft-float -Oz -static -v -Xassembler -G -Xassembler 0 -ffunction-sections -fdata-sections -MD -march=mips32r2 -mtune=4kem -EL -fshort-wchar -fno-zero-initialized-in-bss -fasynchronous-unwind-tables -c -o Coach12p/RfiUiAssetsCompiled1.o -G 0 -x assembl...

...and then getting an x86_64 assembler instead of the MIPS cross-assembler. Adding a -v flag seems to confirm this thinking. With "-ccc-host-triple mips-sde-elf" and the -v flag, I get this invocation to the assembler (-D, -W and -I flags removed): > > "/usr/bin/gcc" -funsigned-char -msoft-float -Oz -static > -v -Xassembler -G -Xassembler 0 -ffunction-sections > -fdata-sections -MD -march=mips32r2 -mtune=4kem -EL > -fshort-wchar -fno-zero-initialized-in-bss > -fasynchronous-unwind-tables -c > -o Coach12p/RfiUiAssetsCo...

On Fri, 20 Aug 2004, Reid Spencer wrote: > On Fri, 2004-08-20 at 18:43, Chris Lattner wrote: > > > I don't understand what you're getting at here. You can change char to > > default to unsigned right now with llvm-gcc -funsigned-char. I don't > > understand how that would change anything to be more useful though. > > The only thing it would change is that character constants with values > > 63 would get encoded in 1 byte instead of 2 (with current > implementation). I'm making a change that wi...

...-EL > > -Xclang -triple -Xclang mipsel-sde-elf > -Xclang -mrelocation-model -Xclang static > > -Xclang -mllvm -Xclang -mips-ssection-threshold=0 > -Xclang -mllvm -Xclang -enable-mips-delay-filler > > -Xassembler -G -Xassembler 0 -g > > -funsigned-char > -fshort-wchar > -fno-zero-initialized-in-bss > -fasynchronous-unwind-tables > -ffunction-sections > -fdata-sections > > -Oz Does that stuff looks like it makes sense? A once-over by someone with some expertise would be much appreciated. I also...

Hi, Ady wrote: > IMHO, the adequate way to solve the problem is finding why vesamenu.c32 > triggers a problem when it is compiled with gcc v.5+. I agree. Currently i am riddling why copy_sysappend_string() should be invoked at all. txt/syslinux.cfg.txt obviously describes the .cfg interface of readconfig.c:record() as "SYSAPPEND" and its flag values. Rawhide-Live-Xfce-628.iso

On Wed, Aug 15, 2012 at 10:17 PM, Carl Norum <carl at lytro.com> wrote: >> -march=mips32r2 >> -mtune=4kem >> -msoft-float >> -EL >> >> -Xclang -triple -Xclang mipsel-sde-elf >> -Xclang -mrelocation-model -Xclang static >> >> -Xclang -mllvm -Xclang -mips-ssection-threshold=0 >> -Xclang -mllvm -Xclang

...> I'd rather that they not be treated specially. If char defaulted to > > unsigned char, there would be little reason to create this special case. > >I don't understand what you're getting at here. You can change char to >default to unsigned right now with llvm-gcc -funsigned-char. I don't >understand how that would change anything to be more useful though. Well, in the old days, char strings were handled just like any other kind of array of primitive types. In that world, when char defaulted to signed char, most of the heavily used ASCII symbols took two by...

...le -Xclang mipsel-sde-elf > > -Xclang -mrelocation-model -Xclang static > > > > -Xclang -mllvm -Xclang -mips-ssection-threshold=0 > > -Xclang -mllvm -Xclang -enable-mips-delay-filler > > > > -Xassembler -G -Xassembler 0 -g > > > > -funsigned-char > > -fshort-wchar > > -fno-zero-initialized-in-bss > > -fasynchronous-unwind-tables > > -ffunction-sections > > -fdata-sections > > > > -Oz > > Does that stuff looks like it makes sense? A once-over by someone with > s...

On Mon, 2004-08-23 at 19:46, Robert Mykland wrote: > At 06:43 PM 8/20/2004, Chris Lattner wrote: > >I don't understand what you're getting at here. You can change char to > >default to unsigned right now with llvm-gcc -funsigned-char. I don't > >understand how that would change anything to be more useful though. > > Well, in the old days, char strings were handled just like any other kind > of array of primitive types. And, they still are :) > In that world, when char defaulted to signed >...

...a little tree of consequential signedness changes or questionable cast operations. How about the following instead ? if ((c >= 0 && c <= ' ') || c == '\x7f') { Besides code improvement there is the riddle of how gcc 5 can spoil the result. > gcc does have an -funsigned-char option. So question to poma: Can it be that the tested installation of gcc 5 uses this option by default ? I read through the mailing list archive but could not find a mail where you tell the compiler version which produces working binaries. Additionally to the different signedness of char,...

At 09:37 PM 8/23/2004, you wrote: >On Mon, 2004-08-23 at 19:46, Robert Mykland wrote: > > At 06:43 PM 8/20/2004, Chris Lattner wrote: > > >I don't understand what you're getting at here. You can change char to > > >default to unsigned right now with llvm-gcc -funsigned-char. I don't > > >understand how that would change anything to be more useful though. > > > > Well, in the old days, char strings were handled just like any other kind > > of array of primitive types. > >And, they still are :) No. If you define an array of i...

...le -Xclang mipsel-sde-elf > > -Xclang -mrelocation-model -Xclang static > > > > -Xclang -mllvm -Xclang -mips-ssection-threshold=0 > > -Xclang -mllvm -Xclang -enable-mips-delay-filler > > > > -Xassembler -G -Xassembler 0 -g > > > > -funsigned-char > > -fshort-wchar > > -fno-zero-initialized-in-bss > > -fasynchronous-unwind-tables > > -ffunction-sections > > -fdata-sections > > > > -Oz > > Does that stuff looks like it makes sense? A once-over by someone with some...

This version contains a fix to mbr.asm, plus a version of Murali's menu system, but ported to gcc. Although gcc produces much bigger 16-bit code (since it's really 32-bit code with prefixes) I figured it would be much easier for people to deal with since it requires the configuration to be compiled in. That being said, it's a *very* powerful menu system, partially *because*

On 08/16/2013 01:42 PM, Renato Golin wrote: > On 16 August 2013 20:02, reed kotler <rkotler at mips.com > <mailto:rkotler at mips.com>> wrote: > > -std=gnu89 is not valid for c++ > > > I think the point here is that this is the default std for GCC but not > Clang, so you have to force clang to behave like GCC. For C++, you'll > have to force

...he gcc version have an influence ? > (C does not specify the signedness of char, but i never saw > a compiler which represented char other than as signed char.) > ... on x86. It is actually ABI specific. On PowerPC (I think) "unsigned char" is the default. gcc does have an -funsigned-char option. -hpa

...char c; while ((c = *src++)) { - if (c <= ' ' || c == '\x7f') { + if ((c >= 0 && c <= ' ') || c == '\x7f') { > > Besides code improvement there is the riddle of how gcc 5 > can spoil the result. > >> gcc does have an -funsigned-char option. > > So question to poma: > > Can it be that the tested installation of gcc 5 uses this > option by default ? See for yourself is it so or not: $ rpm -qf /usr/lib/rpm/rpmrc rpm-4.12.0.1-17.fc23.x86_64 $ grep optflags /usr/lib/rpm/rpmrc | grep 86 optflags: fat -O2 -g...

I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick