Displaying 20 results from an estimated 100 matches similar to: "memdisk patch"
2017 Apr 15
2
[Bug 1146] New: configure ignores enable-static=yes
https://bugzilla.netfilter.org/show_bug.cgi?id=1146
Bug ID: 1146
Summary: configure ignores enable-static=yes
Product: libmnl
Version: unspecified
Hardware: x86_64
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: libmnl
Assignee: pablo at netfilter.org
2009 Nov 20
0
[PATCH] memdisk: Use boot_lba logic for booting an offset within the di
The previous MEMDISK El Torito code merge did not actually work without
this.
Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca>
---
memdisk/setup.c | 17 +++++++++--------
1 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/memdisk/setup.c b/memdisk/setup.c
index 40f3f8c..5a45f39 100644
--- a/memdisk/setup.c
+++ b/memdisk/setup.c
@@ -338,6 +338,7 @@ struct geometry
2014 Jan 03
1
EFI build problems
On 01/02/2014 10:12 PM, Ady wrote:
>
>> On 01/02/2014 04:09 AM, Ferenc Wagner wrote:
>>>
>>> Issuing another make after this gave the previous error again:
>>>
>>> isolinux.asm:1102: error: TIMES value -4 is negative
>>>
>>
>> I just fixed this one... it seems to be a consequence of merging in the
>> MOVZX isolinux fix into
2001 Dec 11
0
VirtualProtect and app crash: what's your interpretation?
Here is my thought process on why the application crashes with a
protection violation reading a section of memory.
I used IDA to disassemble the app. Here's the section where it reads
from memory and crashes because of a protection violation:
00760D4A sub_760D4A proc near ; CODE XREF:
sub_75FCB0+159^Xp
00760D4A push ebp
00760D4B mov
2019 Mar 04
2
Where's the optimiser gone (part 11): use the proper instruction for sign extension
Compile with -O3 -m32 (see <https://godbolt.org/z/yCpBpM>):
long lsign(long x)
{
return (x > 0) - (x < 0);
}
long long llsign(long long x)
{
return (x > 0) - (x < 0);
}
While the code generated for the "long" version of this function is quite
OK, the code for the "long long" version misses an obvious optimisation:
lsign: # @lsign
mov
2018 Nov 20
2
A pattern for portable __builtin_add_overflow()
Hi LLVM, clang,
I'm trying to write a portable version of __builtin_add_overflow() it a way
that the compiler would
recognize the pattern and use the add_overflow intrinsic / the best
possible machine instruction.
Here are docs about these builtins:
https://clang.llvm.org/docs/LanguageExtensions.html#checked-arithmetic-builtins
.
With unsigned types this is easy:
int uaddo_native(unsigned
2014 Jan 03
0
EFI build problems
> On 01/02/2014 04:09 AM, Ferenc Wagner wrote:
> >
> > Issuing another make after this gave the previous error again:
> >
> > isolinux.asm:1102: error: TIMES value -4 is negative
> >
>
> I just fixed this one... it seems to be a consequence of merging in the
> MOVZX isolinux fix into the firmware branch.
>
> -hpa
>
Although the current
2011 Mar 19
2
[LLVMdev] Apparent optimizer bug on X86_64
Compiling a simple automaton created by GNU bison with -O1 or -O2
resulted in the following machine code:
1300 /*-----------------------------.
1301 | yyreduce -- Do a reduction. |
1302 `-----------------------------*/
1303 yyreduce:
1304 /* yyn is the number of a rule to reduce with. */
1305 yylen = yyr2[yyn];
0x0000000000400c14 <rpcalc_parse+628>: mov
2014 Jan 02
4
EFI build problems
On 01/02/2014 04:09 AM, Ferenc Wagner wrote:
>
> Issuing another make after this gave the previous error again:
>
> isolinux.asm:1102: error: TIMES value -4 is negative
>
I just fixed this one... it seems to be a consequence of merging in the
MOVZX isolinux fix into the firmware branch.
-hpa
2011 Mar 19
0
[LLVMdev] Apparent optimizer bug on X86_64
On Sat, Mar 19, 2011 at 1:44 AM, Csaba Raduly <rcsaba at gmail.com> wrote:
> Compiling a simple automaton created by GNU bison with -O1 or -O2
> resulted in the following machine code:
>
> 1300 /*-----------------------------.
> 1301 | yyreduce -- Do a reduction. |
> 1302 `-----------------------------*/
> 1303 yyreduce:
> 1304 /* yyn is the number
2013 Nov 26
3
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
Hi,
hpa wrote:
> - mov dx,cx
> + movzx edx,cx
Gerardo Exequiel Pozzi:
> Yes! Fixed :)
> (maybe garbage in high word of "edx"?)
I am now pondering too, why my machine booted from high LBAs.
I understand that the new code zeros the upper 16 bit of EDX.
Was there remaining garbage from early BIOS activity before
isolinux.bin got started ?
Does my
2014 Jan 03
1
EFI build problems, fixed in which git repo
On 01/02/2014 09:59 PM, Geert Stappers wrote:
> Op 2014-01-02 om 15:37 schreef H. Peter Anvin:
>> On 01/02/2014 04:09 AM, Ferenc Wagner wrote:
>>>
>>> Issuing another make after this gave the previous error again:
>>>
>>> isolinux.asm:1102: error: TIMES value -4 is negative
>>>
>>
>> I just fixed this one... it seems to be a
2008 Nov 22
5
[RFC][PATCH] Gfxboot COMBOOT module
So here it is. Ugly and far from acceptable shape but nonetheless it seems to
work. Parts are borrowed from syslinux core and of course the gfxboot patch for
syslinux 3.63.
Syntax: gfxboot.com <bootlogo file>
- Sebastian
--- /dev/null 2007-09-21 23:50:58.000000000 +0200
+++ syslinux-3.73-pre6/modules/gfxboot.asm 2008-11-22 19:01:10.000000000 +0100
@@ -0,0 +1,883 @@
+ absolute 0
2009 Apr 27
3
Question about vk_check and rllunpack
I am hitting a problem on syslinux-3.80-pre1-2-g6c0fb9e (only last label in config file is found),
but don't want to "cry wolf" (again), so let's start with a question:
ui.inc:
;
; Now check if it is a "virtual kernel"
;
vk_check:
mov esi,[HighMemSize] ; Start from top of memory
.scan:
cmp esi,[VKernelEnd]
jbe
2009 Apr 05
3
[PATCH] Gfxboot COMBOOT module
This is the latest version of the gfxboot module. It's supposed to work on
all Syslinux derivatives.
I am not sure about the copyright notice and would appreciate any input.
- Sebastian
Index: syslinux-3.74-pre17-2-g2a9ddec/modules/Makefile
===================================================================
--- syslinux-3.74-pre17-2-g2a9ddec.orig/modules/Makefile
+++
2018 Nov 06
4
Rather poor code optimisation of current clang/LLVM targeting Intel x86 (both -64 and -32)
Hi @ll,
while clang/LLVM recognizes common bit-twiddling idioms/expressions
like
unsigned int rotate(unsigned int x, unsigned int n)
{
return (x << n) | (x >> (32 - n));
}
and typically generates "rotate" machine instructions for this
expression, it fails to recognize other also common bit-twiddling
idioms/expressions.
The standard IEEE CRC-32 for "big
2011 Aug 06
4
[PATCH] ifmemdsk.c32: Allow boot options based on presence of MEMDISK
Below, attached, and available at the 'ifmemdsk' branch at:
http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e
Review welcome!
- Shao Miller
-----
From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001
From: Shao Miller <shao.miller at yrdsb.edu.on.ca>
Date: Sat, 6 Aug 2011 05:24:46 -0400
Subject: [PATCH]
2018 Nov 27
2
Rather poor code optimisation of current clang/LLVM targeting Intel x86 (both -64 and -32)
"Sanjay Patel" <spatel at rotateright.com> wrote:
> IIUC, you want to use x86-specific bit-hacks (sbb masking) in cases like
> this:
> unsigned int foo(unsigned int crc) {
> if (crc & 0x80000000)
> crc <<= 1, crc ^= 0xEDB88320;
> else
> crc <<= 1;
> return crc;
> }
To document this for x86 too: rewrite the function
2018 Nov 28
2
Rather poor code optimisation of current clang/LLVM targeting Intel x86 (both -64 and -32)
On Wed, Nov 28, 2018 at 7:11 AM Sanjay Patel via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Thanks for reporting this and other perf opportunities. As I mentioned
> before, if you could file bug reports for these, that's probably the only
> way they're ever going to get fixed (unless you're planning to fix them
> yourself). It's not an ideal situation, but
2013 Nov 26
0
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/25/2013 06:32 PM, H. Peter Anvin wrote:
> On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote:
>>
>> I made some more and more experiments beyond LBA 65535
>>
>> Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size
>> 34816)
>>
>> Does not work: * isolinux-5.01.bin (size 34816) * isolinux-5.10.bin
>> (size 36864) *