search for: search&h

Displaying 7 results from an estimated 7 matches for "search&h".

2017 Feb 20
3
[PATCH] Correct chain.c32 v. 6.04-pre1 for Reactos
...:0x8000:0x8100". References: https://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/notes.txt?revision=73859&view=markup&pathrev=73859#l24 https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/notes.txt;hb=HEAD https://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=grep&s=FREELDR_BASE https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/arch/pc/x86common.h;h=c747d145cb3b35f68caab5291dc65dcdca21f17d;hb=HEAD#l17 https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/arch/p...
2017 Mar 04
1
[PATCH] Update chain.c32 v. 6.04-pre1 for current Reactos
...:0x8000:0x8100". References: https://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/notes.txt?revision=73859&view=markup&pathrev=73859#l24 https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/notes.txt;hb=HEAD https://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=grep&s=FREELDR_BASE https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/arch/pc/x86common.h;h=c747d145cb3b35f68caab5291dc65dcdca21f17d;hb=HEAD#l17 https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/arch/p...
2018 Mar 20
3
[LLD/ELF] - Should we implement .note.gnu.property and/or Intel CET in LLD ?
...msg00285.html. GCC started to support it recently and already uses it for building libobjc, libgfortran, libmpx, libstdc++-v3, libatomic, libbacktrace and other libs: * https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3c0f15b4cebccdbb6388a8df5933e69c9b773149 * https://gcc.gnu.org/git/?p=gcc.git&a=search&h=743b05ae4918eac3437965016649b2cabbdbb819&st=commit&s=intel+cet Technology is backwards compatible. I used GCC version 8.0.1 20180319 (experimental) for experiments. For following code and invocations: 1.cpp: int xxx() { return 1; } /usr/local/bin/gcc 1.cpp -c -o test1.o -fcf-protect...
2008 Mar 01
2
contributing to wine project
Hi im interested in contributing to the wine project by doing coding for them. I can program in c i have been for a while now. But i've never really contributed to anything, never realleased bug fixes or anything. I'm just looking for some advice on how to get started i've looked at the website at the development section but i don't think it really explains how to get started. I
2017 Feb 23
0
[PATCH] Correct chain.c32 v. 6.04-pre1 for Reactos
...; References: > https://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/notes.txt?revision=73859&view=markup&pathrev=73859#l24 > > https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/notes.txt;hb=HEAD > > https://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=grep&s=FREELDR_BASE > > https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/arch/pc/x86common.h;h=c747d145cb3b35f68caab5291dc65dcdca21f17d;hb=HEAD#l17 > > https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeld...
2018 Mar 20
0
[LLD/ELF] - Should we implement .note.gnu.property and/or Intel CET in LLD ?
...GCC started to support it recently and already uses it for building > libobjc, libgfortran, libmpx, libstdc++-v3, libatomic, libbacktrace and other libs: > * https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3c0f15b4cebccdbb6388a8df5933e69c9b773149 > * https://gcc.gnu.org/git/?p=gcc.git&a=search&h=743b05ae4918eac3437965016649b2cabbdbb819&st=commit&s=intel+cet > > Technology is backwards compatible. I used GCC version 8.0.1 20180319 > (experimental) for experiments. > For following code and invocations: > 1.cpp: > int xxx() { return 1; } > > /usr/local/bi...
2008 May 30
1
Archive of "bad" things during rsync?
Hi, Wouldn't you know, I can't get rsync to throw an error during a copy. :) I need to put together some instructions for a guy that runs a WISP for him to look over before weekly backups are made (I'll be copying the files to /dev/null so any read errors can be caught). I can do the simple : rsync warning: some files vanished before they could be transferred (code 24) at