Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] broken build?"
2004 Sep 25
0
[LLVMdev] broken build?
This should be fixed. Sorry for the breakage. I forgot to commit a bunch
of files.
Reid.
On Fri, 2004-09-24 at 20:33, Brian R. Gaeke wrote:
> Hi Reid,
>
> You've got a TimeValue.cpp which it looks like you just added to lib/System,
> but I can't compile it on Darwin because there's no Darwin/TimeValue.cpp.
> This breaks my ppc build. I'm not sure what TimeValue
2004 Sep 25
2
[LLVMdev] broken build?
Here are the FreeBSD and Win32 versions of TimeValue.cpp (along with all
the other Win32 changes I've submitted that have yet to be comitted).
Note there is a bug in all the Unix versions in that the time is not
being converted from the Posix origin of 1/1/1970.
On Fri, 24 Sep 2004 22:06:37 -0700
Reid Spencer <reid at x10sys.com> wrote:
> This should be fixed. Sorry for the
2004 Sep 25
1
[LLVMdev] broken build?
>Here are the FreeBSD and Win32 versions of TimeValue.cpp (along with all
>the other Win32 changes I've submitted that have yet to be comitted).
Please give me a hint when the files are committed... I have some fixes to
commit, too.
Thanks.
Henrik
_________________________________________________________________
F� alle de nye og sjove ikoner med MSN Messenger
2014 Mar 19
3
[LLVMdev] getElapsedWallTime unnecessary heap allocation and memory leak
In the file \lib\Support\Process.cpp on line 60, it seems as though an unnecessary heap allocation and memory leak occurs.
This is the offending code:
static TimeValue getElapsedWallTime() {
static TimeValue &StartTime = *new TimeValue(TimeValue::now());
return TimeValue::now() - StartTime;
}
The issue is that the StartTime variable's value is allocated on the heap, after which a
2004 Dec 14
2
[LLVMdev] __time_t type instead of __time64_t in win32/TimeValue.cpp
Hi,
Is it necessary to use the VC6.1+ `__time64_t' type instead of __time_t in
win32/TimeValue.cpp?
---------------
In file included from
c:/projects/src/llvm-1/llvm/lib/System/TimeValue.cpp:51:
c:/projects/build/MinGW/llvm-1-1/lib/System/platform/TimeValue.cpp: In
member function `std::string llvm::sys::TimeValue::toString() const':
2004 Dec 14
0
[LLVMdev] __time_t type instead of __time64_t in win32/TimeValue.cpp
I'm not sure. Perhaps Jeff Cohen knows as he wrote this.
Reid.
On Tue, 2004-12-14 at 11:51, Henrik Bach wrote:
> Hi,
>
> Is it necessary to use the VC6.1+ `__time64_t' type instead of __time_t in
> win32/TimeValue.cpp?
>
> ---------------
> In file included from
> c:/projects/src/llvm-1/llvm/lib/System/TimeValue.cpp:51:
>
2004 Dec 14
1
[LLVMdev] __time_t type instead of __time64_t inwin32/TimeValue.cpp
Replace __time_t with time_t in my question. I've compiled function:
std::string TimeValue::toString() const {
// Alas, asctime is not re-entrant on Windows...
//hb: __time64_t ourTime = this->toEpochTime();
time_t ourTime = this->toEpochTime();
//hb: char* buffer = ::asctime(::_localtime64(&ourTime));
char* buffer = ::asctime(::localtime(&ourTime));
std::string
2014 Mar 19
2
[LLVMdev] getElapsedWallTime unnecessary heap allocation and memory leak
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Bryan Keiren
> Subject: [LLVMdev] getElapsedWallTime unnecessary heap allocation and memory leak
> In the file \lib\Support\Process.cpp on line 60, it seems as though an
> unnecessary heap allocation and memory leak occurs.
> static TimeValue getElapsedWallTime() {
> static
2014 Mar 19
2
[LLVMdev] getElapsedWallTime unnecessary heap allocation and memory leak
On Wed, Mar 19, 2014 at 6:18 PM, Bryan Keiren <
bryan.keiren at guerrilla-games.com> wrote:
> We are indeed trying to completely clean the heap before exiting main().
>
Which means that you either don't have threads, or you join all threads
before main exits.
Is that the case?
Good for you if so!
>
>
> -----Original Message-----
> From: Caldarale, Charles R
2006 Aug 09
4
[LLVMdev] Demo Script Paths
Hello,
I'm trying to get the demo script to run llvm2cpp so that people can get
familiar with the LLVM C++ API through the online demo. However, it
seems that the path used doesn't include llvm2cpp (not updated in a
while?). The demo script currently uses these paths on Zion:
/home/vadve/criswell/box/x86/llvm-gcc/bin/
/home/vadve/gaeke/llvm/Release/bin
/home/vadve/gaeke/bin
2002 Nov 21
1
[LLVMdev] top of tree build failures
See attached build (gmake -k) log.
--
gaeke at uiuc.edu
-------------- next part --------------
gmake[1]: Entering directory `/scratch/scratch0/gaeke/llvm-497cz/utils/Burg'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/scratch/scratch0/gaeke/llvm-497cz/utils/Burg'
gmake[1]: Entering directory `/scratch/scratch0/gaeke/llvm-497cz/lib'
gmake[2]: Entering
2006 Aug 10
0
[LLVMdev] Demo Script Paths
> I'm trying to get the demo script to run llvm2cpp so that people can get
> familiar with the LLVM C++ API through the online demo. However, it
> seems that the path used doesn't include llvm2cpp (not updated in a
> while?). The demo script currently uses these paths on Zion:
I can look into this, but I would strongly suggest not messing with the
demo script until 2-3
2005 Sep 19
2
[LLVMdev] LLVM-TV web page link is broken?
Sorry, I don't personally have any of that stuff anymore -- I seem
to recall that page didn't have a whole lot on it, though. I think
Misha has messed around with llvm-tv more recently than I have. If
you really want that particular page, it looks like you can get (a
version of) it from the Internet Archive...
http://web.archive.org/web/20041102220954/llvm.cs.uiuc.edu/~gaeke/llvm-tv/
2006 Aug 10
2
[LLVMdev] Demo Script Paths
It's already messed with, but there's no harm. If someone turns on the
llvm2cpp option, then they get an error message at the bottom of the
output page. All other output is normal. So, there's no harm in it.
If/when llvm2cpp becomes available on Zion, people then the llvm2cpp
output will appear. Note that llvm2cpp is a 1.8 release feature. My
change was to help people learning LLVM
2004 Nov 01
0
[LLVMdev] Final Visual Studio Patches
If you're getting this error in lib/System/Win32/TimeValue.cpp, then you are not building it correctly. This file is included by lib/System/TimeValue.cpp, which is what you ought to be building. None of the files under Win32 are to be compiled directly; they are all included by files in lib/System.
On Mon, 01 Nov 2004 11:14:18 +0100
Morten Ofstad <morten at hue.no> wrote:
> Hello,
2006 Aug 10
0
[LLVMdev] Demo Script Paths
> It's already messed with, but there's no harm. If someone turns on the
> llvm2cpp option, then they get an error message at the bottom of the
> output page. All other output is normal. So, there's no harm in it.
> If/when llvm2cpp becomes available on Zion, people then the llvm2cpp
> output will appear. Note that llvm2cpp is a 1.8 release feature. My
> change was
2006 Aug 10
2
[LLVMdev] Demo Script Paths
The demo script isn't part of the release and its not failing.
Do you want me to revert the changes?
Reid.
On Thu, 2006-08-10 at 10:08 -0700, Tanya M. Lattner wrote:
> > It's already messed with, but there's no harm. If someone turns on the
> > llvm2cpp option, then they get an error message at the bottom of the
> > output page. All other output is normal. So,
2004 May 21
1
[LLVMdev] Re: LLVMdev digest, Vol 1 #292 - 4 msgs
Hi,
Thank Brian Gaeke so much.
Following TraceBasicBlocks.cpp, I modified the code as below and could insert instruction or function I need into anywhere in Module.
But it works well without BB->getInstList().push_back(InstrCall), and if I add the BB->getInstList().push_back() following new CallInst(), I got error information when runing opt. What is the reason for it? And is it necessary
2006 Aug 10
0
[LLVMdev] Demo Script Paths
> The demo script isn't part of the release and its not failing.
>
> Do you want me to revert the changes?
No. I just said that we should avoid anymore changes for the next 2
weeks to maintain stability.
-Tanya
>
> Reid.
>
> On Thu, 2006-08-10 at 10:08 -0700, Tanya M. Lattner wrote:
>>> It's already messed with, but there's no harm. If someone turns on
2015 Jun 10
2
[LLVMdev] Self-compiling clang on Windows
I'm trying to get clang 3.6.1 to compile itself on Windows, using this
command line:
msbuild /p:Configuration=Release /p:CLToolExe=clang-cl.exe
/p:CLToolPath=c:\llvm\build\Release\bin\ /p:TrackFileAccess=false
/p:Platform="x64" /fileLogger ALL_BUILD.vcxproj
It barfed on an occurrence of __try but that was only in a test file so I
commented it out and retried. Now it's getting