Displaying 20 results from an estimated 31 matches for "cmdarg".
Did you mean:
cmdargs
2015 Jul 22
2
[LLVMdev] (no subject)
Hello,
I have tried a lot fix this error but am not able to can you please
find me a solution am trying to compile the SAFECode in Cygwin Environment
to work for windows.
used make -j4 command to make the files in cygwin i have got this error
make[5]: Leaving directory
'/home/uidr7475/Work/LLVM_OBJ/projects/safecode/tools/clang/include'
/usr/bin/cp: cannot stat
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
...t; > > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
> > >
> > > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
> > > CmdArgs.push_back("-backend-option");
> > > CmdArgs.push_back("-mattr=-altivec");
> > > }
> >
> > Perfect, Hal, thanks! That makes good sense. I'll fix this and also
> > bring some of the CPU handling more up-to-date (several missing
> &g...
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
...t; Off of the top of my head...
>
> Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
>
> if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
> CmdArgs.push_back("-backend-option");
> CmdArgs.push_back("-mattr=-altivec");
> }
Perfect, Hal, thanks! That makes good sense. I'll fix this and also
bring some of the CPU handling more up-to-date (several missing
processors that ought to be in there).
Thanks,
Bill
>...
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
...ead...
> >
> > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
> >
> > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
> > CmdArgs.push_back("-backend-option");
> > CmdArgs.push_back("-mattr=-altivec");
> > }
>
> Perfect, Hal, thanks! That makes good sense. I'll fix this and also
> bring some of the CPU handling more up-to-date (several missing
> processors that ought to be...
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
...thin the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
> > > >
> > > > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
> > > > CmdArgs.push_back("-backend-option");
> > > > CmdArgs.push_back("-mattr=-altivec");
> > > > }
> > >
> > > Perfect, Hal, thanks! That makes good sense. I'll fix this and also
> > > bring some of the CPU handling more up-to-date...
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
...can
> accomplish this?
Off of the top of my head...
Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
CmdArgs.push_back("-backend-option");
CmdArgs.push_back("-mattr=-altivec");
}
Why this not done currently I don't know.
-Hal
>
> Thanks! I appreciate any help.
>
> Bill
>
> --
> Bill Schmidt, Ph.D.
> IBM Advance Toolchain for PowerLinux
> IBM Li...
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
The problem I'm trying to solve: Invoking clang on PowerPC with
-fno-altivec has no effect.
>From what I've been able to piece together, PPC.td specifies various
CPUs and the processor features available on each. So for example we
have:
def FeatureAltivec : SubtargetFeature<"altivec","HasAltivec", "true",
2014 Nov 03
8
[LLVMdev] [PATCH] Protection against stack-based memory corruption errors using SafeStack
...NSTALL_PREFIX
#include "clang/Driver/Compilation.h"
#include "clang/Driver/Driver.h"
diff --git a/lib/Driver/Tools.cpp b/lib/Driver/Tools.cpp
index d11fa4e..7f24995 100644
--- a/lib/Driver/Tools.cpp
+++ b/lib/Driver/Tools.cpp
@@ -2172,6 +2172,29 @@ static void addProfileRT(
CmdArgs.push_back(Args.MakeArgString(LibProfile));
}
+static void addSafeStackRT(
+ const ToolChain &TC, const ArgList &Args, ArgStringList &CmdArgs) {
+ if (!Args.hasFlag(options::OPT_fsafe_stack,
+ options::OPT_fno_safe_stack, false))
+ return;
+
+ const char *L...
2008 Apr 07
1
R_SHARE_DIR not defined for use in tests/Makefile running under Windows
...R_HOME)/share
instead (seems to work OK)?
I notice the following in /src/gnuwin32/front-ends/rcmdfn.c (from R-alpha
2008-04-06), which would suggest that the intention was that R_SHARE_DIR
should be defined... (and I assume it would propagate to to be available in
a Makefile.)
int rcmdfn (int cmdarg, int argc, char **argv)
{
/* tasks:
find R_HOME, set as env variable
set R_SHARE_DIR as env variable
set PATH to include R_HOME\bin
set PERL5LIB to %R_SHARE_DIR%/perl;%Perl5LIB%
set TEXINPUTS to %R_SHARE_DIR%/texmf;%TEXINPUTS%
set HOME if unset...
2013 Jan 21
1
[LLVMdev] Testing canaries
Dear LLVMers,
I am trying to measure the performance overhead (if any) of the
canaries that clang inserts in the code. I would like to do this
automatically, using the LLVM test infra-structure. However, I am not sure
if that is possible. Could someone tell me which flags in the
TEST.nightly.Makefile script, (or any other script) I must change to have
this done? Usually I insert canaries with
2013 Aug 22
0
[LLVMdev] [RFC PATCH] X32 ABI support for Clang/compiler-rt (Clang patch)
.../ld64.so.1";
+ else if (ToolChain.getTriple().getEnvironment() ==
llvm::Triple::GNUX32)
+ return "/libx32/ld-linux-x32.so.2";
else
return "/lib64/ld-linux-x86-64.so.2";
}
@@ -6125,8 +6127,12 @@
}
else if (ToolChain.getArch() == llvm::Triple::systemz)
CmdArgs.push_back("elf64_s390");
- else
- CmdArgs.push_back("elf_x86_64");
+ else if (ToolChain.getArch() == llvm::Triple::x86_64)
+ CmdArgs.push_back(ToolChain.getTriple().getEnvironment() ==
+ llvm::Triple::GNUX32
+ ? "elf32_x86_...
2013 Aug 22
1
[LLVMdev] X32 ABI support for Clang/compiler-rt (re: clang patch)
On Thu, 2013-08-22 at 12:29 +0400, Alexey Samsonov wrote:
> On Thu, Aug 22, 2013 at 11:56 AM, Steven Newbury <steve at snewbury.org.uk>wrote:
>
> > On Thu, 2013-08-22 at 11:50 +0400, Alexey Samsonov wrote:
> > > On Thu, Aug 22, 2013 at 11:39 AM, Steven Newbury <steve at snewbury.org.uk
> > >wrote:
> > >
> > > > On Thu, 2013-08-22 at
2010 Sep 15
1
running 'make' failed during vignette creation ('R CMD build') on Windows
Hi,
This is a follow-up to the problem reported here:
https://stat.ethz.ch/pipermail/r-devel/2010-September/058460.html
After I updated R-2.12 to 2010-09-13 r52905 on the Bioc build system,
some of the packages that have a Makefile in <pkg>/inst/doc still
don't build on Windows. For example, 'R\bin\R.exe CMD build adSplit'
gives:
* checking for file
2013 Oct 01
3
[LLVMdev] RFH: passing options from clang down to opt
.../Tools.cpp
@@ -3594,6 +3594,11 @@ void Clang::ConstructJob(Compilation &C, const
JobAction &JA,
D.Diag(diag::err_drv_argument_not_allowed_with)
<< "-fomit-frame-pointer" << A->getAsString(Args);
+ if (Args.hasArg(options::OPT_fauto_profile)) {
+ CmdArgs.push_back("-auto-profile");
+ }
+
// Claim some arguments which clang supports automatically.
// -fpch-preprocess is used with gcc to add a special marker in the output to
2013 Aug 22
7
[LLVMdev] [RFC PATCH] X32 ABI support for Clang/compiler-rt
Hi,
I'm working on bringing up complete coverage for a Gentoo x32 "desktop"
system. I've been cooking up quite a few patches for various packages
to push upstream, but right now, the biggest blocker is the lack of
support for building with/codegen targeting x32 in llvm/clang. Since
the x32 patches were sent last year, I see support code has landed in
LLVM, and basic handling of
2013 Aug 22
3
[LLVMdev] [NEW PATCH] X32 ABI support for Clang/compiler-rt (Clang patch)
.../ld64.so.1";
+ else if (ToolChain.getTriple().getEnvironment() ==
llvm::Triple::GNUX32)
+ return "/libx32/ld-linux-x32.so.2";
else
return "/lib64/ld-linux-x86-64.so.2";
}
@@ -6125,8 +6127,12 @@
}
else if (ToolChain.getArch() == llvm::Triple::systemz)
CmdArgs.push_back("elf64_s390");
- else
- CmdArgs.push_back("elf_x86_64");
+ else if (ToolChain.getArch() == llvm::Triple::x86_64)
+ CmdArgs.push_back(ToolChain.getTriple().getEnvironment() ==
+ llvm::Triple::GNUX32
+ ? "elf32_x86_...
2017 Nov 06
5
RFC: Debug info for Cuda
Hi everybody,
As you know, Cuda/NVPTX target has very limited support of the debug info in Clang/LLVM. Currently, LLVM supports only emission of the line numbers debug info.
This is caused by limitations of the Cuda/NVPTX codegen. Clang/LLVM translates the source code to LLVM IR, which is then lowered to PTX (parallel thread execution) intermediate file. This PTX file represents special kind of
2020 May 27
2
By default clang does not emit trap insn
looks like experimental/work in progress support:
https://reviews.llvm.org/D62731
On Tue, May 26, 2020 at 10:39 PM kamlesh kumar via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
>
> On Wed, May 27, 2020 at 11:06 AM kamlesh kumar <kamleshbhalui at gmail.com>
> wrote:
>
>> Hi Devs,
>> going by this link https://llvm.org/docs/LangRef.html#floatenv
>>
2011 Jul 29
0
[LLVMdev] sparc assembly code generation with 2.9/final clang and llvm
....ll
--> clang: warning: unknow platform, assuming -mfloat-abi=soft
--> error: error reading 'soft'
In order to get rid of this error, I commented
clang/lib/Driver/Tools.cpp:L680.
I wonder whether there are any significant the side-effects from
commenting "CmdArgs.push_back("soft");"
Also, can anyone explain the significance of the option
-ccc-host-triple sparc-unknown-linux?
Thanks,
Gangryung
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/201107...
2001 Jan 11
0
problem with strptime example (and mention of bug.report) (PR#811)
...("9Feb1960", "%d%b%Y")
[1] "NA"
Stephen
p.s. I failed to send this using bug.report(); on DEC OSF/1, "mailx"
does not recognise the -c switch for setting the carbon copy (CC)
field, causing an error. One solution might be to remove the -c
argument from the cmdarg in bug.rerport(), or put a
"~c joe@bloggs.com" directive at the end of the file to set the CC field.
--please do not edit the information below--
Version:
platform = alphaev56-dec-osf4.0f
arch = alphaev56
os = osf4.0f
system = alphaev56, osf4.0f
status =
major = 1
minor = 2.0...