search for: sdy

Displaying 20 results from an estimated 327 matches for "sdy".

Did you mean: say
2018 May 07
2
[clang] Running a single testcase
On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com> wrote: > The simplest way to run a clang test case that I know of is to clone both > llvm and clang repos, run all the tests, then run an individual test. > > IIRC like so: > > git clone llvm ...... > cd llvm/tools > git clone clang ..... > cd ../../ > mkdir build > cd build > cmake
2018 May 07
0
[clang] Running a single testcase
> On 7 May 2018, at 11:01, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com <mailto:brian.cain at gmail.com>> wrote: >> The simplest way to run a clang test case that I know of is to clone both >> llvm and clang repos, run all the tests, then run an individual test. >>
2008 Sep 02
2
SDI support works correctly (sdi.c32)
Hi, As I have not seen any confirmation yet on the list, I just wanted to let you know that sdi.c32 works fine here, at least as fine as my initial syslinux-2.11 asm patch. I only use XPe SDI images with the following structure (of course PART blob size can vary): Type Offset Size Base Address Attr ---- ------------------- -------------------
2018 May 07
2
[clang] Running a single testcase
On Mon, May 7, 2018 at 4:03 PM, Amara Emerson <aemerson at apple.com> wrote: > On 7 May 2018, at 11:01, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > > On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com> wrote: > > The simplest way to run a clang test case that I know of is to clone both > llvm and clang repos, run all the
2018 May 07
0
[clang] Running a single testcase
The simplest way to run a clang test case that I know of is to clone both llvm and clang repos, run all the tests, then run an individual test. IIRC like so: git clone llvm ...... cd llvm/tools git clone clang ..... cd ../../ mkdir build cd build cmake ../llvm ninja check-clang ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c On Sun, May 6, 2018 at 7:10 AM, Sedat Dilek via llvm-dev <
2018 May 06
3
[clang] Running a single testcase
Hi, while experimenting with llvmlinux on Debian/testing AMD64 I wanted to run some x86-64 ASM tests. I fell over [1] and wanted to run it. So, I cloned clang from Git... $ git clone https://github.com/llvm-mirror/clang.git I looked through some docs where I have seen I need "llvm-lit" or "lit.py". The Debian package llvm-7-tools from <apt.llvm.org> does ship
2006 Feb 23
7
Bug in setting GUI to SDI mode?
Hi I did a google search on this and came up with nothing. OK, in the latest release of R for windows, I want to change the gui to SDI mode. Edit -> GUI preferences Choose SDI Apply I get the message about properties not being able to be changed on a running console, and that I need to save. So I click Save, and am met with a "Save As" dialogue box with the default file called
2012 Jan 11
1
R CMD check pkg and 32/64 bit.
R gurus: I'm trying to get another round of rconifers out and I need some advice/help crushing differences in the examples test. I'm trying to make sure the max sdi values are being respected. I've added a tests/rconifers-Ex.Rout.save (from windows i386-pc-mingw32) and when I ran R CMD check (both R-2.13.0), I got the following results: * using log directory
2008 Apr 09
4
SYSLINUX 3.63-pre4
I have tackled a major bug that affected sdi.c32 especially, but might at least theoretically have affected other formats as well. It *appears* to load the SDI image I managed to stitch together with XP Embedded Studio, but it doesn't actually boot neither on my system nor in simulation; then trying to upgrade it to SP2 caused it to corrupt itself, so I'm not all that keen to trying
2004 Oct 02
2
patch: SDI Xpe images support for pxelinux
Hi, I added support in pxelinux for SDI (Wndows XP embedded images) files a few time ago for specific needs. It works well (at least for me atm) and I think I can now submit it to this list. I get a very good improvement in speed over the traditional way of loading SDI images. * Links : The 'diff -urN' patch for syslinux-2.11 (documentation included) :
2018 Aug 29
2
LLVM/Clang version 7.0.0rc2 fails with gcc (Debian 8.2.0-4)
On Wed, Aug 29, 2018 at 9:29 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Wed, Aug 29, 2018 at 7:51 AM, Matthias Klose <doko at debian.org> wrote: >> On 28.08.2018 13:55, Sedat Dilek wrote: >>> On Tue, Aug 28, 2018 at 10:59 AM, Hans Wennborg <hans at chromium.org> wrote: >>>> On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev
2009 Jan 14
2
Windows installer text bug (PR#13445)
Full_Name: Rob Cranfill Version: 2.8.1 OS: Windows XP SP2 Submission from: (NULL) (130.76.32.19) Using the Windows installer for 2.8.1, partway through the process there is a dialog that looks something like this: ---------------------------------------------- Display Mode Do you prefer the MDI or SDI interface? ------- Please specify MDI or SDI, then click Next. (*) MDI (one big
2018 Aug 29
3
Get full cmake lines and prepocessed source for a GCC bug report
On Wed, Aug 29, 2018 at 10:14 AM, Hans Wennborg <hans at chromium.org> wrote: > On Wed, Aug 29, 2018 at 9:45 AM, Sedat Dilek via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC >> mainatiners want two things... >> >> [ FULL CMAKE LINE ] >> >> How do I
2008 Apr 17
2
Question about RAID 5 array rebuild with mdadm
I'm using Centos 4.5 right now, and I had a RAID 5 array stop because two drives became unavailable. After adjusting the cables on several occasions and shutting down and restarting, I was able to see the drives again. This is when I snatched defeat from the jaws of victory. Please, someone with vast knowledge of how RAID 5 with mdadm works, tell me if I have any chance at all
2008 Apr 08
1
SYSLINUX 3.63-pre3 release candidate; SDI image booting
Hello, I just received a serious bug report from Stas Kysel of rPath (with a great test case); it appears that deleted files can confuse extlinux so that it misses files. This is bad. As a result, I have pushed out 3.63-pre3, and intend to make a 3.63 final shortly. I would appreciate any help testing this. Furthermore, I would like to finish the SDI booting module, but I have yet to
2008 Mar 31
1
SDI loading patch
If someone could try it out and let me know if it works, I would appreciate it... (also, if someone can actually send me an .sdi image, for testing only, I would also appreciate it...) http://www.zytor.com/~hpa/syslinux/0001-COM32-module-to-load-a-Microsoft-System-Deployment-I.patch -hpa
2018 Aug 27
2
LLVM/Clang version 7.0.0rc2 fails with gcc (Debian 8.2.0-4)
Hi, I have not sent yet any bug-reports to llvm-dev but I am seeing this build-failure: ... [574/3685] Building CXX object lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o FAILED: lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o /usr/bin/g++-8 -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
2001 Feb 08
0
[CORE SDI ADVISORY] SSH1 CRC-32 compensation attack detector vulnerability
CORE SDI http://www.core-sdi.com SSH1 CRC-32 compensation attack detector vulnerability Date Published: 2001-02-08 Advisory ID: CORE-20010207 Bugtraq ID: 2347 CVE CAN: CAN-2001-0144 Title: SSH1 CRC-32 compensation attack detector vulnerability Class: Boundary Error Condition Remotely Exploitable: Yes Locally Exploitable: Yes Release Mode:
2014 Aug 30
2
PXE booting WinPE with UEFI architecture
> Date: Fri, 29 Aug 2014 13:02:10 +0100 > From: Michael Brown <mcb30 at ipxe.org> > To: Jason Jones <jason.s.jones at convergys.com>, "syslinux at zytor.com" > <syslinux at zytor.com> > Subject: Re: [syslinux] PXE booting WinPE with UEFI architecture > Message-ID: <54006BC2.3090703 at ipxe.org> > Content-Type: text/plain;
2014 Aug 30
0
PXE booting WinPE with UEFI architecture
On Fri, Aug 29, 2014 at 8:01 PM, Spike White <spikewhitetx at gmail.com> wrote: > But chain-loading into WinPE would be useful too. > In order to use "wimboot", I have to use ./efi64/com32/modules/pxechn.c32 > to chain-load into ipxe? As so: pxechn.c32 contains BIOS-only code and is not going to work in any EFI environment. > LABEL WinPE > MENU LABEL