Displaying 20 results from an estimated 3000 matches similar to: "Small inconsistencies in configure checks"
2023 Dec 02
1
Small inconsistencies in configure checks
On Sat, Dec 02, 2023 at 10:24:57PM +0300, Vitaly Chikunov wrote:
> JFYI. I am not sure it's worth reporting but, when building 2.5.5 for ALT
Talking of small inconsistencies, 2.5.5 isn't a Xapian version...
> I noticed small inconsistencies in configure output.
>
> 1. xapian-binding:
>
> checking for /usr/bin/rdoc... no
> checking for rdoc... /usr/bin/rdoc
>
2014 Sep 30
2
[LLVMdev] size_t?
I'm getting compile errors because size_t is getting redefined. My
"forced include file" starts with:
#if BUILDING_FOR_WINDOWS
#define NOMINMAX
/* deal with the fact that windef.h also defines BOOL */
#define BOOL WINBOOL
#include <windows.h>
#include <intrin.h>
#undef BOOL
#endif
Looking at the preprocessor expansion of a typical .cpp file, I see that
crtdefs.h
2014 Sep 30
2
[LLVMdev] size_t?
Hi Reid,
I copied the x64 toolsets by hand; they got installed to C:\Program
Files (x86)\LLVM\tools\msbuild\x64; they just didn't get moved correctly
by install.bat.
I just verified that the LLVM-vs2013 toolset.props is correct.
If it is a bitness problem, perhaps I'm failing to define something
correctly?
Regards,
Eric
On 9/30/14, 11:29 AM, Reid Kleckner wrote:
> This looks
2013 Sep 14
3
PATCH: x86-64 support and SSE intrinscis code
Erik de Castro Lopo wrote:
> When should FLAC__HAS_X86INTRIN be defined? What header file should I be
> checking for?
Ah, should be checking for <x86intrin.h>.
The rest seems to be coming together. Testing this now.
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
2014 Oct 01
2
[LLVMdev] size_t?
I believe that we provide a definition of size_t inside the compiler itself
when clang is in MSVC compatibility mode.
On Tue, Sep 30, 2014 at 5:51 PM, Eric Mader <emader at gmx.us> wrote:
> I did some more investigation of the size_t size error. I misunderstood
> what was happening. It turns out that size_t is already defined before my
> prefix header is included. I added the
2014 Oct 01
2
[LLVMdev] size_t?
We inject a typedef for size_t here:
http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Sema/Sema.cpp?revision=218230&view=markup#l206
The typedef type is determined by calling getSizeType().
SizeType is (relevantly) calculated in two places:
X86_64
http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Basic/Targets.cpp?revision=218666&view=markup#l3512
X86_32
2020 Jun 08
7
Misc patches
Hi,
Here are 3 suggested patches.
1. Build test for cmake and run the test in gitlab-ci.
2. Disable the message box on Windows on abort that cause test hangs in CI.
3. Build time improvement by removing unnecessary includes of stdio.h in production code and change to a lighter header intrin.h -> intrin0.h (windows only). Attached screenshot of measurement but it resulted in 14%
2020 Jun 11
1
Misc patches
3, no good catch attached is an updated patch
//Marcus
________________________________
From: Jean-Marc Valin <jmvalin at jmvalin.ca>
Sent: Thursday, June 11, 2020 10:49
To: Marcus Asteborg <xnorpx at outlook.com>; opus at xiph.org <opus at xiph.org>
Subject: Re: [opus] Misc patches
On 2020-06-08 01:39, Marcus Asteborg wrote:
> 1. Build test for cmake and run the test in
2014 Oct 02
3
problems with configure.ac
1) in config.h FLAC__HAS_X86INTRIN macro is always defined and empty,
even if x86intrin.h is not available.
2) sse_os is defined as 'yes' or 'no', but AM_CONDITIONAL tests it for 'true':
AM_CONDITIONAL(FLaC__SSE_OS, test "x$sse_os" = xtrue)
It seems that it should be changed to
AM_CONDITIONAL(FLaC__SSE_OS, test "x$sse_os" = xyes)
3) configure
2019 Aug 18
1
1.3.3: powerpc portability problems
The PowerPC-related changes in FLAC 1.3.3 have caused some portability
problems.
libFLAC/cpu.c assumes that the <sys/auxv.h> header and the getauxval()
function are universally available on PowerPC platforms. They are not.
On FreeBSD/powerpc, <sys/auxv.h> is available, but getauxval() is
not. Equivalent functionality is provided by elf_aux_info().
On OpenBSD/powerpc, neither is
2020 Jun 12
2
Misc patches
Sorry about that, let me check the correct version for the intrin0.h include guard.
//Marcus
________________________________
From: Ralph Giles <giles at thaumas.net>
Sent: Thursday, June 11, 2020 19:31
To: Marcus Asteborg <xnorpx at outlook.com>; opus at xiph.org <opus at xiph.org>
Subject: Re: [opus] Misc patches
Speaking of needing more complete ci feedback, the intrin0.h
2011 Feb 28
1
[LLVMdev] [cfe-dev] [PATCH] Windows improvements
Hello Erik,
Thank you to work. I have not checked to build them, though, I can
tell you some comments, excuse me.
* General
- Please post patches to cfe-commits and to llvm-commits, too.
(IMHO it would not be needed to split articles apart each lists as
long as each would be related.)
- If you can, please attach files w/o CRLF(dos encodings), or with
attached text/plain.
- You may
2015 Jun 12
2
[LLVMdev] Self compiling latest clang from SVN
Makes sense, yeah, trying something in a different environment is usually a
good way to find problems. I had indeed moved the renamed clang-cl.exe to a
different directory, but when I move it back into its home directory and
retry the build, I get the same errors.
On Thu, Jun 11, 2015 at 11:16 PM, Reid Kleckner <rnk at google.com> wrote:
> Thanks for trying the self-host, it's
2006 Jan 26
4
[LLVMdev] VS2005 patch
OK, fixed the problem with the intrin.h header that doesn't exist in previous versions of VS...
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: JIT.patch
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060126/7e55b0d0/attachment.ksh>
2014 Oct 13
2
[PATCH] for configure.ac
lvqcl wrote:
> lvqcl wrote:
>
> > 1) in config.h FLAC__HAS_X86INTRIN macro is always defined and empty,
> > even if x86intrin.h is not available.
> >
> > 2) sse_os is defined as 'yes' or 'no', but AM_CONDITIONAL tests it for 'true':
>
> The patch is attached. Please check it.
Looks good. I need to do a little testing.
> > 3)
2019 Feb 05
2
debugging installation problem
Sorry in advance for the limited details.
I have a build of a recent (Monday) llvm/clang which I have installed in the expected way in my environment but I am getting failures like this;
In file included from <some directory>/lib/clang/stable/include/x86intrin.h:29:
In file included from <some directory>/lib/clang/stable/include/immintrin.h:118:
<some
2013 Sep 08
7
PATCH: x86-64 support and SSE intrinscis code
It's not possible to use ia32/*.nasm code in 64-bit compiles.
There's still no 64-bit asm code in FLAC. I'm not familiar with asm too,
so I wrote SSE-accelerated code using intrinsics.
This code uses two new preprocessor macros:
FLAC__CPU_X86_64 (analogous to FLAC__CPU_IA32)
and FLAC__HAS_X86INTRIN (analogous to FLAC__HAS_NASM)
Patch for cpu.c/cpu.h adds CPU features (sse3, ssse3)
2019 Feb 05
2
debugging installation problem
Given they in separate repos, is there a way to to verify which revisions go together? Is it enough that the clang (shortly) after llvm in time?
On 2/5/19, 1:03 PM, "Eric Christopher" <echristo at gmail.com> wrote:
Your clang and your llvm don't match, they're often version locked and
you need to make sure both of them are the same-ish revision.
-eric
2006 Jan 26
0
[LLVMdev] VS2005 patch
On Thu, 26 Jan 2006, Morten Ofstad wrote:
> OK, fixed the problem with the intrin.h header that doesn't exist in previous
> versions of VS...
applied, thanks!
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060123/031225.html
-Chris
--
http://nondot.org/sabre/
http://llvm.org/
2020 Aug 19
2
Question about llvm vectors
Hi,
I love llvm vectors, yet I wonder why some advanced vector operations are
specific to some CPU targets?
Let me take an example:
/// Horizontally adds the adjacent pairs of values contained in two
/// 128-bit vectors of [4 x float].
///
/// \headerfile <x86intrin.h>
///
/// This intrinsic corresponds to the <c> VHADDPS </c> instruction.
///
/// \param __a
/// A