search for: dogfooding

SmartFTP installs but fails to start with: "Fatal Error: sfFTPLib.dll is not registered correctly" http://www.smartftp.com/download/ System: Fedora 9 Wine: 1.0 rc2

Who really uses strikethroughs?? This is one of the most common tripwires in RedCloth. You are the friend--the only friend--who has offered to help. Obviously em dashes. I died in -2006- wait, no, two-thousand-FIVE! Obviously strikethrough. I''m going on a trip - a long one - to the Virgin Islands. That''s got to be en dashes. Such a cheap, no-hassle, no-worry

Michael Johnson via llvm-dev <llvm-dev at lists.llvm.org> writes: > Hi Rui, > > Are there any plans to support the -defsym command line option? It doesn't look that hard, it was just never requested. What project is using it? Cheers, Rafael

console output: bash-3.1# wine Advanced\ IP\ Scanner.exe err:ipaddress:IPADDRESS_GetPartIndex We subclassed the wrong window! (hwnd=0x70034) err:ipaddress:IPADDRESS_GetPartIndex We subclassed the wrong window! (hwnd=0x3004c) err:ipaddress:IPADDRESS_GetPartIndex We subclassed the wrong window! (hwnd=0x30058) err:ipaddress:IPADDRESS_GetPartIndex We subclassed the wrong window! (hwnd=(nil))

Windows (stable) version tested in Wine. Needs Java 1.5 minimum. Available at www.jedit.org, source code available. Installation without an hitch. After installation, it asks you wether you want to start it. If you tick on yes, it is immediately prompted. Afterwards, your screen becomes black with only the main block (middle) to be seen. No possibility to close it and the rest is black. You can

On Wed, Mar 15, 2017 at 11:41 AM, Mark Kettenis via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Or perhaps we can cheat and include "GNU" somewhere in the > lld -v output ;). Let's please not do this. It would give the wrong signal. If libtool won't acknowledge lld's existence, then there are better ways like a rewrite and (temp) downstream patch.

On Tue, Mar 14, 2017 at 12:07 PM, Mark Kettenis <mark.kettenis at xs4all.nl> wrote: > > Date: Tue, 14 Mar 2017 11:39:22 -0700 > > From: Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> > > > > Hi all, > > > > LLVM 4.0.0 is out, and I can say that LLD/ELF is now ready for production > > use at least for x86-64 (and probably for AArch64 and

...compiler will work fine, but anything built with a compiler from > ports will silently generate non-working binaries. Fortunately for LLVM, > this includes building a non-working tablegen, so the build fails rather > than appearing to succeed and giving non-working binaries. > > For dogfooding purposes, it would be very helpful if the LLVM CMake files > allowed you to specify the suffix for the system clang and LLD to use in a > single place. Currently, telling it to use lld will pass -fuse-ld=lld, but > we typically need to actually pass -fuse-ld=lld40 or -fuse-ld=lld-devel to...

On Wed, Mar 15, 2017 at 6:02 PM, Ed Maste <emaste at freebsd.org> wrote: > Note that even if/when we get changes incorporated into libtool it > will still take a long time for the change to appear in new releases > of software packages using libtool. A downstream patch to the libtool > package in various operating systems or distributions doesn't really > help that much

For dogfooding the compiler I normally use is a LTO bootstrap of clang. On linux that is simple to do that since clang passes the correct plugin to the linker. On OS X ld64 uses libLTO.so it finds via DYLD_LIBRARY_PATH. Should clang set that before running the linker? Is there a better way for clang to tell the...

Michael Johnson <mpj at rowley.co.uk> writes: > Hi Rafael, >> Michael Johnson via llvm-dev <llvm-dev at lists.llvm.org> writes: >> >>> Hi Rui, >>> >>> Are there any plans to support the -defsym command line option? >> It doesn't look that hard, it was just never requested. What project is >> using it? > Not sure I understand

I personally haven't tried gdb_index, and I don't know the quality of the produced index. Most of the code was written by George. One thing I noticed about the feature (and filed as http://bugs.llvm.org/show_bug.cgi?id=32228) is that our gdb_index feature is much slower than the gold. Apparently there's room for improvement. On Thu, Mar 16, 2017 at 8:35 AM, David Blaikie <dblaikie

Hi all, LLVM 4.0.0 is out, and I can say that LLD/ELF is now ready for production use at least for x86-64 (and probably for AArch64 and MIPS). I believe you've heard a few good news about the linker -- it just works <http://lld.llvm.org/#features> and is very fast <http://lld.llvm.org/#performance>, clean, compact and supported by the active community. I don't think I need to

...symlink, it properly load my custom libLTO.dylib library. According to the ld64 sources, it should have an other way to do that (using the -lto_library option), but I never managed to make it work. Le 12 nov. 2013 à 15:53, Rafael Espíndola <rafael.espindola at gmail.com> a écrit : > For dogfooding the compiler I normally use is a LTO bootstrap of clang. > > On linux that is simple to do that since clang passes the correct > plugin to the linker. > > On OS X ld64 uses libLTO.so it finds via DYLD_LIBRARY_PATH. Should > clang set that before running the linker? Is there a be...

...es. For instance, I'd otherwise would have to make an assumption about the threading model the platform has (or assume there are no threads at all, which prevents me from allowing goroutine like ("run parallel till you need to write to a channel") behavior). Right now I'm sort-of dogfooding my work by trying to get Go running on dragonegg. I've discovered some small issues already (for instance I need to save R10 somewhere when compiling a function with a nest parameter). I'll send a revised set of patches within sometime this week, addressing all such issues I can find. That...

What program did you use to test the feature, and what was missing information? I'd like to file that as a bug so that we can fix this later. On Thu, Mar 16, 2017 at 2:34 PM, David Blaikie <dblaikie at gmail.com> wrote: > FWIW - selfhosting I did find that GDB wasn't able to find the source code > for some functions when using LLD's gdb_index, so I've switched back to

Hi all ! During this GSoC, I've worked on improving the llvm binutils suite. I've wrote a final [1]report for those of you who would be interested. Regards, -- Paul Semel [1] http://paulsemel.org/posts/command-line-replacements-in-llvm-binutils/

...re confusing. > > Hum, for me it would be less confusing. :) > > GCC uses bfd by default, LLVM uses LLD. If you want to change, use > -fuse-ld. > > What would be confusing in this scenario? > In practice, I think your proposal can be read for most people as a proposal to do dogfooding LLD more widely in LLVM by making it the default linker. I've been using LLD as default for a long period of time (probably a year) and saw no problem. So it should be doable. Do people okay with that? Probably, as long as it works, no one would really care, maybe? > > > Clang's...

On Thu, Mar 16, 2017 at 11:26 AM, Ed Maste via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 15 March 2017 at 16:34, Carsten Mattner <carstenmattner at gmail.com> > wrote: > > > > If FreeBSD's libtool is patched to be aware of the base ld=lld, > > would this still be true? > > Yes, for the same reason Joerg points out in another reply in this

On Wed, May 22, 2013 at 8:33 PM, Charles Davis <cdavis5x at gmail.com> wrote: > > On May 22, 2013, at 5:14 PM, Eric Christopher wrote: > > > Hi All, > > > > Can anyone see good a reason not to move to cmake as our only build > > configuration system and drop future support for autoconf + makefiles > > now that 3.3 has branched? > +1. > - CMake