Displaying 17 results from an estimated 17 matches for "__date__".
2015 May 21
3
[LLVMdev] Proposal: change LNT’s regression detection algorithm and how it is used to reduce false positives
...trategy to work and so the google guys are usually on top of any issues in
this respect (thanks google guys!).
> I know it is supposed to be. Does anyone have any data to show this is
> going to be an effective approach? It seems like there are benchmarks in
> the test-suite which use __DATE__ and __TIME__ in them. I assume that will
> be a problem?
>
__DATE__ and __TIME__ should be easy to solve by modifying the benchmark,
or teaching clang to always return a fixed value for them (maybe we already
have this? IIRC google's build system does something like this; or maybe
the do...
2015 May 26
0
[LLVMdev] Proposal: change LNT’s regression detection algorithm and how it is used to reduce false positives
...or its caching strategy to work and so the google guys are usually on top of any issues in this respect (thanks google guys!).
I know it is supposed to be. Does anyone have any data to show this is going to be an effective approach? It seems like there are benchmarks in the test-suite which use __DATE__ and __TIME__ in them. I assume that will be a problem?
__DATE__ and __TIME__ should be easy to solve by modifying the benchmark, or teaching clang to always return a fixed value for them (maybe we already have this? IIRC google's build system does something like this; or maybe the do it at the...
2015 May 21
4
[LLVMdev] Proposal: change LNT’s regression detection algorithm and how it is used to reduce false positives
On 20 May 2015 at 23:31, Sean Silva <chisophugis at gmail.com> wrote:
> In the last 10,000 revisions of LLVM+Clang, only 10 revisions actually
> caused the binary of MultiSource/Benchmarks/BitBench/five11 to change. So if
> just store a hash of the binary in the database, we should be able to pool
> all samples we have collected while the binary is the the same as it
>
2015 May 28
2
[LLVMdev] Proposal: change LNT’s regression detection algorithm and how it is used to reduce false positives
...so the google guys are usually on top of any
> issues in this respect (thanks google guys!).
>
> I know it is supposed to be. Does anyone have any data to show
> this is going to be an effective approach? It seems like there
> are benchmarks in the test-suite which use __DATE__ and __TIME__
> in them. I assume that will be a problem?
>
> __DATE__ and __TIME__ should be easy to solve by modifying the
> benchmark, or teaching clang to always return a fixed value for them
> (maybe we already have this? IIRC google's build system does something
>...
2015 May 28
2
[LLVMdev] Proposal: change LNT’s regression detection algorithm and how it is used to reduce false positives
...or its caching strategy to work and so the google guys are usually on top of any issues in this respect (thanks google guys!).
I know it is supposed to be. Does anyone have any data to show this is going to be an effective approach? It seems like there are benchmarks in the test-suite which use __DATE__ and __TIME__ in them. I assume that will be a problem?
__DATE__ and __TIME__ should be easy to solve by modifying the benchmark, or teaching clang to always return a fixed value for them (maybe we already have this? IIRC google's build system does something like this; or maybe the do it at the...
2015 May 28
0
[LLVMdev] Proposal: change LNT’s regression detection algorithm and how it is used to reduce false positives
...rk and so the google guys are usually on top of any issues in this respect (thanks google guys!).
>>
>>
>> I know it is supposed to be. Does anyone have any data to show this is going to be an effective approach? It seems like there are benchmarks in the test-suite which use __DATE__ and __TIME__ in them. I assume that will be a problem?
>>
>> __DATE__ and __TIME__ should be easy to solve by modifying the benchmark, or teaching clang to always return a fixed value for them (maybe we already have this? IIRC google's build system does something like this; or may...
2012 Jul 13
2
[LLVMdev] Dealing with a corrupted /proc/self/exe link
...=============================================================
--- autoconf/configure.ac (revision 160127)
+++ autoconf/configure.ac (working copy)
@@ -647,6 +647,20 @@
AC_DEFINE_UNQUOTED([ENABLE_TIMESTAMPS],$ENABLE_TIMESTAMPS,
[Define if timestamp information (e.g., __DATE__) is allowed])
+dnl Enable reading of the "/proc/self/exe" link.
+AC_ARG_ENABLE(proc-self-exe,
+ AS_HELP_STRING([--enable-proc-self-exe],
+ [Enable reading of the "/proc/self/exe" link (default is YES)]),,
+ enableval=default)
+case "$enable...
2015 Jun 02
3
[LLVMdev] Proposal: change LNT’s regression detection algorithm and how it is used to reduce false positives
...rategy to work and so the google guys are usually on top of any issues in this respect (thanks google guys!).
>
>
> I know it is supposed to be. Does anyone have any data to show this is going to be an effective approach? It seems like there are benchmarks in the test-suite which use __DATE__ and __TIME__ in them. I assume that will be a problem?
>
> __DATE__ and __TIME__ should be easy to solve by modifying the benchmark, or teaching clang to always return a fixed value for them (maybe we already have this? IIRC google's build system does something like this; or maybe the d...
2015 May 28
1
[LLVMdev] Proposal: change LNT’s regression detection algorithm and how it is used to reduce false positives
...rategy to work and so the google guys are usually on top of any issues in this respect (thanks google guys!).
>
>
> I know it is supposed to be. Does anyone have any data to show this is going to be an effective approach? It seems like there are benchmarks in the test-suite which use __DATE__ and __TIME__ in them. I assume that will be a problem?
>
> __DATE__ and __TIME__ should be easy to solve by modifying the benchmark, or teaching clang to always return a fixed value for them (maybe we already have this? IIRC google's build system does something like this; or maybe the d...
2016 May 03
8
RFC: Should the default LLVM build be deterministic?
Hello LLVM-Dev,
Today if a user checks out LLVM, configures with no options specified, and builds the result is non-deterministic. Meaning if you clean and build again the binaries are not identical. This impacts all target platforms equally and is caused by the default value of LLVM_ENABLE_TIMESTAMPS being On.
I believe this is incorrect behavior, and I’m curious what the wider community
2015 Jul 07
4
[LLVMdev] Recording hash of binaries in test-suite and LNT.
...ink some due
> diligence is necessary. Is clang *really* that deterministic,
> especially over successive revs? I know it is supposed to be. Does
> anyone have any data to show this is going to be an effective approach?
> It seems like there are benchmarks in the test-suite which use __DATE__
> and __TIME__ in them. I assume that will be a problem?
>
> > On May 21, 2015, at 1:43 AM, Renato Golin <renato.golin at linaro.org>
> wrote:
> >
> > On 20 May 2015 at 23:31, Sean Silva <chisophugis at gmail.com> wrote:
> >> In the last 10,000 revis...
2012 Jul 13
0
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
...======================================
> --- autoconf/configure.ac (revision 160127)
> +++ autoconf/configure.ac (working copy)
> @@ -647,6 +647,20 @@
> AC_DEFINE_UNQUOTED([ENABLE_TIMESTAMPS],$ENABLE_TIMESTAMPS,
> [Define if timestamp information (e.g., __DATE__) is allowed])
>
> +dnl Enable reading of the "/proc/self/exe" link.
> +AC_ARG_ENABLE(proc-self-exe,
> + AS_HELP_STRING([--enable-proc-self-exe],
> + [Enable reading of the "/proc/self/exe" link (default is YES)]),,
> + enableva...
2014 Apr 04
2
[LLVMdev] successful full recurse of mips32
We have NFS mounted drives.
I first build an clang/llvm hosted compiler for Mips linux using the
clang/llvm linux x86 compiler.
Call this clang1.
then in directory recurse on Mips host, I place this clang1 compiler and
build clang2.
then i rename recurse to recurse1 and create a new recurse directory.
in recurse I copy clang2 from recurse1 to a recurse but name it clang1.
then i build
2012 Jul 13
2
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
...==================
>> --- autoconf/configure.ac (revision 160127)
>> +++ autoconf/configure.ac (working copy)
>> @@ -647,6 +647,20 @@
>> AC_DEFINE_UNQUOTED([ENABLE_TIMESTAMPS],$ENABLE_TIMESTAMPS,
>> [Define if timestamp information (e.g., __DATE__) is allowed])
>>
>> +dnl Enable reading of the "/proc/self/exe" link.
>> +AC_ARG_ENABLE(proc-self-exe,
>> + AS_HELP_STRING([--enable-proc-self-exe],
>> + [Enable reading of the "/proc/self/exe" link (default is YES)]),,
>> +...
2005 Oct 23
2
Is it feasible to cross-build compat5x binary?
Hi folks,
I think we need to update compat5x binary to fix FreeBSD-SA-05:21.openssl,
but will the binaries built by ``make universe'' be identical with actual
build on Alpha, Sparc64, etc? (Yes, I'm volunteering to do the work iff
they are identical ;-)
Cheers,
--
Xin LI <delphij frontfree net> http://www.delphij.net/
See complete headers for GPG key and other information.
2008 Apr 04
0
speexdec 1.2.3
...n");
printf ("Please report bugs to the mailing list `speex-dev at xiph.org'.\n");
}
void version()
{
const char* speex_version;
speex_lib_ctl(SPEEX_LIB_GET_VERSION_STRING, (void*)&speex_version);
printf ("speexdec (Speex decoder) version %s (compiled " __DATE__ ")\n", speex_version);
printf ("Copyright (C) 2002-2006 Jean-Marc Valin\n");
}
void version_short()
{
const char* speex_version;
speex_lib_ctl(SPEEX_LIB_GET_VERSION_STRING, (void*)&speex_version);
printf ("speexdec version %s\n", speex_version);
pri...
2008 Apr 04
2
speexdec 1.2.3
On Fri, Apr 4, 2008 at 12:19 AM, Jean-Marc Valin
<jean-marc.valin at usherbrooke.ca> wrote:
> Jahn, Ray (R.) a ?crit :
>
> > Dear Speex codec community:
> >
> > I am working on conversion of voice files. I could not figure out how to use speexdec.exe 1.2.3 in piped mode in order to avoid the creation of the potentially large intermediate *.wav or *.pcm files. Any