similar to: Syslinux 4.00 released

Displaying 20 results from an estimated 1000 matches similar to: "Syslinux 4.00 released"

2010 Jun 29
9
SYSLINUX 4.00 2010-06-28 EDD Load error - Boot error
SYSLINUX 4.00 2010-06-28 EDD Load error - Boot error Booting from USB on old IBM T43 or newer Esprimo E5731E. No problems with version 3.86 and same usb-stick.
2016 Dec 22
0
struct bitfield regression between 3.6 and 3.9 (using -O0)
On 12/21/2016 4:45 PM, Phil Tomson via llvm-dev wrote: > Here's our testcase: > > #include <stdio.h> > > struct flags { > unsigned frog: 1; > unsigned foo : 1; > unsigned bar : 1; > unsigned bat : 1; > unsigned baz : 1; > unsigned bam : 1; > }; > > int main() { > struct flags flags; > flags.bar = 1; >
2016 Dec 22
2
struct bitfield regression between 3.6 and 3.9 (using -O0)
Here's our testcase: #include <stdio.h> struct flags { unsigned frog: 1; unsigned foo : 1; unsigned bar : 1; unsigned bat : 1; unsigned baz : 1; unsigned bam : 1; }; int main() { struct flags flags; flags.bar = 1; flags.foo = 1; if (flags.foo == 1) { printf("Pass\n"); return 0; } else {
2009 Dec 10
1
[PATCH] [RFC] lib: add a hex dump lib function
Hi all, Date: Thu, 10 Dec 2009 22:55:20 +0800 Subject: [PATCH] [RFC] lib: add a hex dump lib function I think it would be better to have a hex dump routine; it would make debugging much easier since it can dump the data, like fs meta data, in a hex style, just like what the 'hexdump -C file' command does. BTW, I'm not sure where should I to put the hexdump function declaration. For
2018 Apr 09
1
llvm-dev Digest, Vol 166, Issue 22
Hi Krzysztof, Sure, please see below. DAG.dump.() before and after, annotated with what I believe the DAG means. I've spent some time debugging the method but it's proving difficult to determine where the logic is misfiring. Disabling the entire combine causes a lot of failing x86-64 tests - I may have to learn an upstream vector ISA to make progress on this. Thank you >From your
2007 Mar 01
2
[LLVMdev] Version 1.9 SSA form question
int %nlz10(uint %param.x) { %.t3 = shr uint %param.x, ubyte 1 ; <uint> [#uses=1] %.t4 = or uint %.t3, %param.x ; <uint> [#uses=2] %.t7 = shr uint %.t4, ubyte 2 ; <uint> [#uses=1] %.t8 = or uint %.t7, %.t4 ; <uint> [#uses=2] %.t11 = shr uint %.t8, ubyte 4 ; <uint> [#uses=1]
2009 Aug 08
0
[PATCH] core:PXELINUX: fix the OACK option parsing bug.
the current code can just handle one option beacuse I put the do-while loop in the wrong position. Signed-off-by: Liu Aleaxander <Aleaxander at gmail.com> --- core/pxe.c | 26 +++++++++++++------------- 1 files changed, 13 insertions(+), 13 deletions(-) diff --git a/core/pxe.c b/core/pxe.c index 81d3e23..bda1a54 100644 --- a/core/pxe.c +++ b/core/pxe.c @@ -928,20 +928,20 @@ static void
2019 Feb 08
2
Unfolded additions of constants after promotion of @llvm.ctlz.i16 on SystemZ
Hi, SystemZ supports @llvm.ctlz.i64() natively with a single instruction (FLOGR), and lesser bitwidth versions of the intrinsic are promoted to i64. For some reason, this leads to unfolded additions of constants as shown below: This function: define i16 @fun(i16 %arg) {   %1 = tail call i16 @llvm.ctlz.i16(i16 %arg, i1 false)   ret i16 %1 } ,gives this optimized DAG as input to instruction
2017 Sep 14
2
Question about 'DAGTypeLegalizer::SplitVecOp_EXTRACT_VECTOR_ELT'
Hi All, I have a question about splitting 'EXTRACT_VECTOR_ELT' with 'v2i1'. I have a llvm IR code snippet as following: llvm IR code snippet: for.body: ; preds = %entry, %for.cond %i.022 = phi i32 [ 0, %entry ], [ %inc, %for.cond ] %0 = icmp ne <2 x i32> %vecinit1, <i32 0, i32 -23> %1 = extractelement <2 x i1>
2004 Jan 24
2
Re-Post: Combining Factors in model.matrix
Hello, I didn't get any response on this before, leading me to believe I've missed something fundamental. Can anybody guide me in the correct direction for more help on this? Paul ================================================= I want to be able to create a design matrix with two factors. For instance, if I have: > t1 <- factor(c(1,1,2,2)); > t2 <-
2006 Jun 27
1
Boxplot questions.
Dear all, I am having a data for 2 different treatments with different time points. So, I used the following code to plot the boxplot and also to do anova. T11 <- c(280, 336, 249, 277, 429) T12 <- c(400, 397, 285, 407, 313) T13 <- c(725, 373, 364, 706, 249) T21 <- c(589, 257, 466, 248, 913) T22 <- c(519, 424, 512, 298, 907) T23 <- c(529, 479, 634, 354, 1015) obs <- c(T11,
2016 Aug 02
2
Instruction selection problems due to SelectionDAGBuilder
Hello. I'm having problems at instruction selection with my back end with the following basic-block due to a vector add with immediate constant vector (obtained by vectorizing a simple C program doing vector sum map): vector.ph: ; preds = %vector.memcheck50 %.splatinsert = insertelement <8 x i64> undef, i64 %i.07.unr, i32 0
2017 Sep 15
2
Question about 'DAGTypeLegalizer::SplitVecOp_EXTRACT_VECTOR_ELT'
> extends the elements to 8bit and stores them on stack. Store is responsible for zero-extend. This is the policy... - Elena -----Original Message----- From: jingu at codeplay.com [mailto:jingu at codeplay.com] Sent: Friday, September 15, 2017 17:45 To: llvm-dev at lists.llvm.org; Demikhovsky, Elena <elena.demikhovsky at intel.com>; daniel_l_sanders at apple.com Subject: Re: Question
2009 Mar 23
0
GSoC Application submitted.
Hi, all. I have submitted my application just now. it's at: http://socghop.appspot.com/student_proposal/show/google/gsoc2009/aleaxander/t123783762744 Thanks. -- regards liu Aleaxander
2010 Jun 24
2
Syslinux 4.00-pre59 -- last call for 4.00
Hello everyone, I have just released Syslinux 4.00-pre59. This is intended as last call for 4.00: from this point on I will only fix showstopper bugs. Anything that didn't make this release will have to wait for 4.01 or 4.10. Please help test it and report bugs, so we can avoid said showstopper bugs in the actual release. Target date for final release is Monday, June 28. -hpa
2016 Oct 20
2
[AVX512BW] Nasty KAND issue
On 10/20/2016 9:28 AM, Cameron McInally via llvm-dev wrote: > I should have attached the generated asm to save some trouble. > Apologies for that and attaching now... > > > > On Thu, Oct 20, 2016 at 12:26 PM, Cameron McInally > <cameron.mcinally at nyu.edu> wrote: >> On Thu, Oct 20, 2016 at 12:05 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
2017 Feb 28
2
rL296252 Made large integer operation codegen significantly worse.
I see we're missing an isel pattern for add producing carry and doing a memory RMW. I'm going to see if adding that helps anything. ~Craig On Mon, Feb 27, 2017 at 8:47 PM, Nirav Davé via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Yes. I'm seeing that as well. Not clear what's going on. > > In any case it looks to be unrelated to the alias analysis so barring
2010 Apr 01
2
Syslinux 3.86 released; Syslinux 4.00 now in beta test
Syslinux 3.86 is out; it is a bug fix release. Syslinux 4.00, starting with Syslinux 4.00-pre38, is now officially in beta test. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.86: * chain.c32: fix chainloading the MBR of a hard disk (broken in 3.85). * mboot.c32: report the boot loader name in the information structure. *
2010 Mar 18
1
argv[0] doesn't contain module name and cat.c32 hangs with Syslinux 4.00-pre36
The program name of the module can't be retrieved with argv[0]. I tested it by running cat.c32 (com32/samples/cat.c32). In Syslinux 3.85, argv[0] returns an empty string. In Syslinux 4.00-pre36, argv[0] returns some garbage characters. ISOLINUX 3.85 2010-02-20 ETCD Copyright (C) 1994-2010 H. Peter Anvin et al argv = 0x00182c44 argv[0] = 0x07fbffc3 = "" argv[1] = 0x00182c34 =
2009 Aug 07
1
SYSLINUX 4.00-pre1
Hi everyone, I have pushed out a development preview release of Liu's filesystems in C code (including ext4 support for EXTLINUX). It is called 4.00-pre1, which doesn't mean it is the final 4.00 by any means (it isn't even current with respect to some aspects of the 3.8x branch.) However, it is now available for people to try out. It is checked into the fsc branch