Re: Buffer overflow in objdump

2024-11-07 Thread Hans-Peter Nilsson
On Thu, 7 Nov 2024, 2ourc3 1er wrote: > Hi, > > I'd like to report a buffer-overflow in objdump, is this the right place for > it? Not really: please enter bug-regports in https://sourceware.org/bugzilla and thanks in advance! > Thanks, > > 2ourc3 brgds, H-P

Re: PE header copyright issue

2023-12-17 Thread Hans-Peter Nilsson
On Fri, 15 Dec 2023, Joshua Hudson wrote: > I started looking into EFI64 development for reasons, and discovered > something totally unexpected. The Debian grub64 loader and shim both > start with some ancient MS-owned code, and the code is obviously the > same stupid MS owned code that MS uses in

Re: Off-by-one error in ld documentation

2015-09-11 Thread Hans-Peter Nilsson
On Fri, 11 Sep 2015, Mark Rages wrote: > On Tue, Sep 8, 2015 at 2:40 AM, Nick Clifton wrote: > > Hi Hans-Peter, > > > >> Nicely, thanks. While there's a point in keeping just one > >> version for simplicity, the educational point of "here's what > >> you may write which doesn't work, here's the s

Re: Off-by-one error in ld documentation

2015-09-07 Thread Hans-Peter Nilsson
On Mon, 7 Sep 2015, Nick Clifton wrote: > > extern char start_of_ROM[], end_of_ROM[], start_of_FLASH[]; > > memcpy (start_of_FLASH, start_of_ROM, end_of_ROM - start_of_ROM); > > Actually that *is* a nicer way of writing it. With two people agreeing, it's almost an objective view. :) > But, I wrot

Re: Off-by-one error in ld documentation

2015-09-05 Thread Hans-Peter Nilsson
On Thu, 3 Sep 2015, Nick Clifton wrote: > Hi Mark, > > > In ld/ld.texinfo, the following example code is offered: > > > > > start_of_ROM = .ROM; > > > end_of_ROM = .ROM + sizeof (.ROM) - 1; > > > start_of_FLASH = .FLASH; > > > > > > Then the C source code to perform the copy would be: >

Re: Help, my ld is cripled. =(((

2015-01-05 Thread Hans-Peter Nilsson
On Fri, 2 Jan 2015, Alan Grimes wrote: > The LD in my gentoo system is profoundly brain defective. It has no brains, and seems to be working as instructed. > Should I go symlink libncurses > to every path on my entire computer? =P Only for as long as you (and your build system) pass "-nostdlib"

Re: [Bug gas/13215] New: ARM Cortex M3 strexh strexb instructions with same registers generates error

2011-12-21 Thread Hans-Peter Nilsson
On Tue, 20 Dec 2011, DaniBoy wrote: > > To solve this problem with ARM cortex m3 I changed the supplied CMSIS file > core_cm3.c > > I'm now using: > uint32_t __STREXH(uint16_t value, uint16_t *addr) > { >//uint32_t result=0; >register uint32_t result asm ("r2"); >__ASM volatile ("strexh

Re: [Bug gas/5138] Bit range mismatch in config/tc-cris.c

2007-10-09 Thread Hans-Peter Nilsson
On Tue, 9 Oct 2007, karvjorm at users dot sourceforge dot net wrote: --- Additional Comments From karvjorm at users dot sourceforge dot net 2007-10-09 05:09 --- (In reply to comment #1) Well, it's 8-bit signed *and* 8-bit unsigned: perhaps saying "not in 8-bit signed or unsigned rang

Re: [Bug gas/5141] New: 4th range checking mismatch in config/tc-cris.c

2007-10-07 Thread Hans-Peter Nilsson
On Sun, 7 Oct 2007, karvjorm at users dot sourceforge dot net wrote: #: config/tc-cris.c:3653 #, c-format msgid "Value not in 8 bit range: %ld" The error message above is not quite correct, because range 255...-128 is a bit greater than 8 bits. See PR 5140. __

Re: [Bug gas/5140] New: Third bit range checking mismatch in config/tc-cris.c

2007-10-07 Thread Hans-Peter Nilsson
On Sun, 7 Oct 2007, karvjorm at users dot sourceforge dot net wrote: #: config/tc-cris.c:3631 #, c-format msgid "Value not in 16 bit range: %ld" The error message above is not quite correct, because range 0x...-32768 is a bit greater than 16 bits. This is getting tedious, see PR 5139. _

Re: [Bug gas/5139] New: Another bit range checking mismatch in config/tc-cris.c

2007-10-07 Thread Hans-Peter Nilsson
n Sun, 7 Oct 2007, karvjorm at users dot sourceforge dot net wrote: #: config/tc-cris.c:2120 config/tc-cris.c:2171 #, c-format msgid "Immediate value not in 16 bit range: %ld" The error message above is not quite correct, because range -32768...65535 is a bit greater than 16 bits. Same reply

Re: [Bug gas/5138] New: Bit range mismatch in config/tc-cris.c

2007-10-07 Thread Hans-Peter Nilsson
On Sun, 7 Oct 2007, karvjorm at users dot sourceforge dot net wrote: The following error message is a bit limited: #: config/tc-cris.c:2110 config/tc-cris.c:2150 #, c-format msgid "Immediate value not in 8 bit range: %ld" source code: if (instruction->imm_oprnd_size == SIZE_FIELD && (out_insn

Re: [Bug binutils/1860] New: binutils.texi:3495: No such file or directory.

2005-11-12 Thread Hans-Peter Nilsson
On Sat, 12 Nov 2005, danglin at gcc dot gnu dot org wrote: > ../../../src/binutils/doc/binutils.texi:3495: @include [EMAIL PROTECTED]/../li > biberty/at-file.texi': No such file or directory. > ../src/configure --prefix=/home/dave/opt/gnu --host=hppa-linux > --target=hppa64- > linux --disable-nls