Displaying 9 results from an estimated 9 matches for "sourcefilename".
Did you mean:
source_filename
2008 Aug 14
1
the name of the current running script.r
...me I realise there is a possible update to
a script and then I have to copy the new version over all my directories to
overwrite the old scripts. So, it is better to have a script height.r:
# height.r script beg
SourceFileDir <- "f:/documents/data & fits/THz Imaging Lab/r scripts"
SourceFileName <- "height.r"
source(file.path(SourceFileDir, SourceFileName))
# height.r script end
placed in every directory and when running it, it sources the one and only
script height.r (this is the core script file) from a fix place.
But, I need again three/more other scripts depending on the...
2020 May 25
3
Implications of Module SourceFileName
In the language I'm working on, a module (which does have a user-defined
name in source) may be comprised of several files. I'm considering passing
the (user-defined) name to llvm::Module's setModuleIdentifier, then a
semicolon separated list of file names to setSourceFileName. Is this going
to cause unforeseen problems?
https://releases.llvm.org/10.0.0/docs/LangRef.html#source-filename seems to
imply that it only needs to be a "consistent unique global identifier", but
then also shows a unix-style path as the syntax. I don't see anything
crazy being don...
2008 Sep 10
1
peimg /inf running on wine
...**********************
* PrivCopyFileExW (KERNEL32.@)
*
* This implementation ignores most of the extra parameters passed-in into
* the "ex" version of the method and calls the CopyFile method.
* It will have to be fixed eventually.
*/
BOOL WINAPI PrivCopyFileExW(LPCWSTR sourceFilename, LPCWSTR destFilename,
LPPROGRESS_ROUTINE progressRoutine, LPVOID appData,
LPBOOL cancelFlagPointer, DWORD copyFlags)
{
/*
* Interpret the only flag that CopyFile can interpret.
*/
FIXME("src=%s dest=%s prg=0x%08x data=0x%08x fl...
2011 Dec 19
2
[LLVMdev] DwarfDebug craziness
>From DwarfDebug.cpp:
>/// GetOrCreateSourceID - Look up the source id with the given directory and
>/// source file names. If none currently exists, create a new id and insert it
>/// in the SourceIds map. This can update DirectoryNames and SourceFileNames
>/// maps as well.
>unsigned DwarfDebug::GetOrCreateSourceID(StringRef FileName,
> StringRef DirName) {
> // If FE did not provide a file name, then assume stdin.
> if (FileName.empty())
> return GetOrCreateSourceID("<stdin>...
2011 Dec 19
0
[LLVMdev] DwarfDebug craziness
Josh Matthews wrote:
>> From DwarfDebug.cpp:
>
>> /// GetOrCreateSourceID - Look up the source id with the given directory and
>> /// source file names. If none currently exists, create a new id and insert it
>> /// in the SourceIds map. This can update DirectoryNames and SourceFileNames
>> /// maps as well.
>> unsigned DwarfDebug::GetOrCreateSourceID(StringRef FileName,
>> StringRef DirName) {
>> // If FE did not provide a file name, then assume stdin.
>> if (FileName.empty())
>> return GetOrCrea...
2017 Apr 04
3
RFC: Adding a string table to the bitcode format
On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith <
dexonsmith at apple.com> wrote:
>
> On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote:
>
> On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
>>
>> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote:
>>
2018 Mar 26
0
Interest in integrating a linux perf JITEventListener?
...ext(DebugObj);
> +
> + // Use symbol info to iterate functions in the object.
> + for (const std::pair<SymbolRef, uint64_t> &P : computeSymbolSizes(DebugObj)) {
> + SymbolRef Sym = P.first;
> + std::vector<LLVMPerfJitDebugEntry> LineInfo;
> + std::string SourceFileName;
> +
> + Expected<SymbolRef::Type> SymTypeOrErr = Sym.getType();
> + if (!SymTypeOrErr) {
> + // TODO: Actually report errors helpfully.
> + consumeError(SymTypeOrErr.takeError());
> + continue;
> + }
> + SymbolRef::Type SymType = *SymTypeOrE...
2016 Dec 29
1
Interest in integrating a linux perf JITEventListener?
Having something like this available in tree would definitely be
useful. For simplicity, why don't we start with support for the second
style? This is the long term useful one and would be a good starting
point for getting the code in tree. Can you give a pointer to the patch
so that I can assess the rough complexity? If it's simple enough, I'd
be happy to help get it reviewed
2017 Feb 02
0
Interest in integrating a linux perf JITEventListener?
Hi,
On 2016-12-29 13:17:50 -0800, Philip Reames wrote:
> Having something like this available in tree would definitely be
> useful.
Cool.
> For simplicity, why don't we start with support for the second style? This
> is the long term useful one and would be a good starting point for getting
> the code in tree.
Works for me.
> Can you give a pointer to the patch so that