similar to: PIC issues... Linking statically to speex when generating a shared library..

On 12/3/07, Stefan Reuther <streu@gmx.de> wrote: > John Miles wrote: > > What's wrong with a plain old .bat file, or even an NMAKE .mak file? > > Ship two files, debug.bat and release.bat, and call it good. > > > > It is best to leave project-file creation up to individual users, > > in my opinion. > > I second that. When I played around with Speex

I am trying to use the speex echo canceler and preprocessor with sipXtapi to develop a sip user agent. the sipXmedialib call flow graph uses 10ms frames and I am not sure what the implications are if I try to change this. The documentation seemed to indicate that a 20ms frame was recomended, but it didn't go into the consquences of using other frame sizes. We are going to use headsets

What's wrong with a plain old .bat file, or even an NMAKE .mak file? Ship two files, debug.bat and release.bat, and call it good. It is best to leave project-file creation up to individual users, in my opinion. MS changes their IDEs and project-file formats more often than most people change their underwear. The odds that any given open-source project will actually compile without any

http://barakas.servebeer.com/stuff/tc_htb.txt

****************Free sex pic downloads*********************** http://Earnfre.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to

Keir Fraser wrote: > On 13 Sep 2005, at 03:40, Jiang, Yunhong wrote: > >> 1) I think the cpu_reset_interrupt() is a common API on qemu for >> hardware interrupt/exception etc,while clear the shared page is just >> for hardware interrupt. Of course, this function is currently used >> just for hardware interrupt since qemu works as a device model :) >> But

Women in Texas. Nude Pic & Chat http://golddating.servik.com/texas.htm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to

But I am using llvm-gcc-4.2. Any idea why it's failing? Evan On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote: > On Feb 16, 2008, at 7:06 AM, Apache wrote: >> New Test Failures: >> test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU] > > This test doesn't work with gcc-4.0, which caused it to fail on a > number of testers overnight. I can fix that in 4.0, but as I

I have been playing a bit with LLVM again and it looks like the current major missing feature on Linux x86-64 is PIC. Is anyone working on it? If not, I would like to do so. I have the ABI documentation (http://www.x86-64.org/documentation/abi.pdf), but would be glad if someone had some LLVM specific pointers. For example, from the targets that do have support for PIC, which one is the one to be

On May 30, 2008, at 4:34 AM, Apache wrote: > http://llvm.org/nightlytest/test.php?machine=277&night=6245 > Name: grue.apple.com > Nickname: grue-x86-64-pic > Buildstatus: Error: compilation aborted > > Buildlog available at http://llvm.org/nightlytest/machines/2008-05-30_06:33:56-Build-Log.txt That last pathname is not correct, it should be

Hello, Rafael > On linux X86_64, calls to local but externally visible functions > should use the PLT. Access to local (same compilation unit), variables > can just use RIP relative access. Right, this is just optimization. AFAIR, current code already does this for 'normal' PIC - it just checks for linkage and doesn't assemble call via PLT for stuff with internal linkage.

The attached patch adds support for PIC on linux x86-64. It also adds some tests. The patch fixes tests 1, 10 and 11. I would like to keep all tests, since I find the assembler printer code a bit hard to read, and I like to have tests around to find out if a change does what I think it does. With this patch I was able to bootstrap gcc in linux x86-64 with shared libraries enabled :-) Cheers, --

Hello, Rafael > With this patch I was able to bootstrap gcc in linux x86-64 with > shared libraries enabled :-) Awesome! But... -ENOPATCH :( -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

2008/6/6 Anton Korobeynikov <asl at math.spbu.ru>: > Hello, Rafael > > Awesome! But... -ENOPATCH :( Attached now. Thanks, -- Rafael Avila de Espindola Google Ireland Ltd. Gordon House Barrow Street Dublin 4 Ireland Registered in Dublin, Ireland Registration Number: 368047 -------------- next part -------------- A non-text attachment was scrubbed... Name: x86-64-plt.patch Type:

On Fri, 2008-06-06 at 17:08 +0100, Rafael Espindola wrote: > 2008/6/6 Anton Korobeynikov <asl at math.spbu.ru>: > > Hello, Rafael > > > > Awesome! But... -ENOPATCH :( > > Attached now. Hi Rafael, Thanks a lot for working on this! I have one question about the patch; why did you choose too add a new enum, PICCallStyle, instead of reusing (possibly with some

On Jun 6, 2008, at 11:55 AM, Dan Gohman wrote: > On Fri, 2008-06-06 at 17:08 +0100, Rafael Espindola wrote: >> 2008/6/6 Anton Korobeynikov <asl at math.spbu.ru>: >>> Hello, Rafael >>> >>> Awesome! But... -ENOPATCH :( >> >> Attached now. > > Hi Rafael, > > Thanks a lot for working on this! > > I have one question about the

> Yes, please remove PICCallStyle and have printPLT check for pic > relocation model and Subtarget.isTargetELF(). Done. > And where you are modifying this part of the code. Please rename > printGOT, printStub, and printPLT to something that indicates they are > predicate functions. Perhaps shouldPrintGOT, etc.? Done. Updated patch attached. > Thanks, > > Evan Cheers,

Due to the LTO modifications to the build system it is not possible to do old non LTO builds that involve some old PIC behaviour, this means Cygwin and possible other platforms old behaviours is broken, and they are not LTO'ed yet either. Would it be possible to have both the old PIC behaviour and the new LTO based behavious coincide via a flags like --enable-lto=(yes,no) and for older PIC

Is there any overview or detailed socumentation on LLVM PIC ? Many thanks in advance, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090613/8b6b5719/attachment.html>

Could someone give me an overview of the PIC stuff if at all possible. Many thanks, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090615/4defff02/attachment.html>