Displaying 13 results from an estimated 13 matches for "mangled_nam".
Did you mean:
mangled_name
2020 Sep 22
2
Unifying CMake variable names used in checks across subprojects
...and library checks.
I think that this is really unnecessary and could be easily improved by
unifying CMake variable names used in checks across subprojects to benefit
from caching.
I've looked at naming conventions used across all subprojects and I'm
proposing the following:
C_SUPPORTS_${mangled_name}_FLAG for check_c_compiler_flag
CXX_SUPPORTS_${mangled_name}_FLAG for check_cxx_compiler_flag
HAVE_${mangled_name} for check_library_exists
Note: It'd be more consistent for check_library_exists to
use HAS_${mangled_name}_LIB but that's going to cause more churn in LLVM so
that's some...
2020 Sep 22
2
Unifying CMake variable names used in checks across subprojects
...I think that this is really unnecessary and could be easily improved by unifying CMake variable names used in checks across subprojects to benefit from caching.
>
> I've looked at naming conventions used across all subprojects and I'm proposing the following:
>
> C_SUPPORTS_${mangled_name}_FLAG for check_c_compiler_flag
> CXX_SUPPORTS_${mangled_name}_FLAG for check_cxx_compiler_flag
> HAVE_${mangled_name} for check_library_exists
IMO, these issues are a manifestation of the fact that we basically have (at least) 4 times the same overall logic, once for each runtime project:...
2018 May 15
12
[PATCH libldm 00/12] New API: an ability to retrieve created device-mapper devices back after they have been created.
The main goal of these patch series is to implement a new API that allows to retrieve created device-mapper devices for volumes and partitions back after they have been created.
As part of this patch:
- required libdevmapper version was bumped to 1.02. I think it is safe because it was released more then 10 years ago;
- newer version of libdevmapper allowed to simplify code base a little bit;
-
2020 Sep 25
2
Unifying CMake variable names used in checks across subprojects
...is is really unnecessary and could be easily improved by unifying CMake variable names used in checks across subprojects to benefit from caching.
>>
>> I've looked at naming conventions used across all subprojects and I'm proposing the following:
>>
>> C_SUPPORTS_${mangled_name}_FLAG for check_c_compiler_flag
>> CXX_SUPPORTS_${mangled_name}_FLAG for check_cxx_compiler_flag
>> HAVE_${mangled_name} for check_library_exists
>
> IMO, these issues are a manifestation of the fact that we basically have (at least) 4 times the same overall logic, once for each...
2018 Mar 16
2
How to get c++ function demangled name without parameters.
Hi all,
We know that 'ItaniumDemangle' has been added into llvm lib to resolve
demangling related issues.
And if we dump mangled function name '_Z3duti' into 'char
*llvm::itaniumDemangle(const char *mangled_name, char *buf, size_t *n, int
*status)', we will get 'dut(int)'.
So my question is:
How can I just get the function name 'dut' without parameters, like
'(int)', in above case?
(We know that there is a GNU project, named libiberty, which can provide
several different dema...
2018 Mar 16
0
How to get c++ function demangled name without parameters.
...16 2:15 PM, Fangqing Du via llvm-dev wrote:
> Hi all,
>
> We know that 'ItaniumDemangle' has been added into llvm lib to resolve
> demangling related issues.
>
> And if we dump mangled function name '_Z3duti' into 'char
> *llvm::itaniumDemangle(const char *mangled_name, char *buf, size_t *n,
> int *status)', we will get 'dut(int)'.
>
> So my question is:
> How can I just get the function name 'dut' without parameters, like
> '(int)', in above case?
>
> (We know that there is a GNU project, named libiberty, which...
2005 Jan 05
1
rsync filename heuristics
...s on similarity of prefix */
> + for (; *name==*basename && *name; name++, basename++)
> + score++;
> + return score;
> +}
> +
> +int open_alternate_base_fuzzy(const char *fname)
> +{
> + DIR *d;
> + struct dirent *di;
> + char *basename, *dirname;
> + char mangled_name[MAXPATHLEN];
> + char bestname[MAXPATHLEN];
> + unsigned int bestscore = 0;
> + const char *ext;
> +
> + /* FIXME: can we assume fname fits here? */
> + strcpy(mangled_name, fname);
> +
> + split_names(mangled_name, &dirname, &basename);
> + d = opendir(dirname);...
2012 Jul 07
2
[LLVMdev] Crash using the JIT on x86 but work on x64
.../ will only work with non-virtual methods
{
union MethodEntry
{
intptr_t offset;
void* function;
};
return static_cast<const MethodEntry*>(void_cast(&method))->function;
}
static llvm::Type* voidptr_type = NULL;
void registerSymbolFunction(const char* mangled_name, void* func)
{
// This is the JIT way for register a function
// Commented "sig.push_back" before defined function because they don't seem to need args
std::vector<llvm::Type*> sig;
llvm::FunctionType* FT = NULL;
llvm::Function* F = NULL;
sig.clear();...
2004 Jul 14
4
String overflow in safe_strcpy .
...mbd/mangle_hash.c (revision 1298)
> +++ smbd/mangle_hash.c (working copy)
> @@ -546,8 +546,10 @@
> /* Fill the new cache entry, and add it to the cache. */
> s1 = (char *)(new_entry + 1);
> s2 = (char *)&(s1[mangled_len + 1]);
> - safe_strcpy( s1, mangled_name, mangled_len );
> - safe_strcpy( s2, raw_name, raw_len );
> + memcpy( s1, mangled_name, mangled_len );
> + s1[mangled_len] = '\0';
> + memcpy( s2, raw_name, raw_len );
> + s2[raw_len] = '\0';
> ubi_cachePut( mangled_cache, i, new_entr...
2013 Oct 18
1
[RFC/PATCH 2/3] core: MultiFS infrastructure added.
...tructures (we don't have malloc yet...) */
__export struct file files[MAX_OPEN];
@@ -344,6 +349,9 @@ __export int open_file(const char *name, int flags, struct com32_filedata *filed
dprintf("open_file %s\n", name);
+ if (switch_fs(&name))
+ return -1;
+
mangle_name(mangled_name, name);
rv = searchdir(mangled_name, flags);
@@ -361,6 +369,9 @@ __export int open_file(const char *name, int flags, struct com32_filedata *filed
filedata->blocklg2 = SECTOR_SHIFT(file->fs);
filedata->handle = rv;
+ restore_fs();
+ restore_chdir_start();
+
retu...
2012 Aug 20
13
[PATCH 00/12] Multidisk support
Hello,
the following patches should get multidisk access working.
The syntax accepted is the following:
(hdx,y)/path/to/file
where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk.
the other accepted syntax is using MBR's 32 bits disk signature so for example:
(mbr:0x12345678,2)/foo/bar
would address
2017 Jun 21
6
RFC: Cleaning up the Itanium demangler
...>
#include <cstring>
#include <cctype>
#ifdef _MSC_VER
// snprintf is implemented in VS 2015
#if _MSC_VER < 1900
#define snprintf _snprintf_s
#endif
#endif
namespace __cxxabiv1
{
namespace
{
enum
{
unknown_error = -4,
invalid_args = -3,
invalid_mangled_name,
memory_alloc_failure,
success
};
+class string_ref
+{
+ const char *first, *last;
+public:
+ template <size_t N> string_ref(const char (&str)[N])
+ : first(str), last(str + N - 1) {}
+ string_ref(const char* first, const char* last)
+ : first(...
2015 Jul 22
13
[PULL 0/8] MultiFS suppport for BIOS and EFI
So last week I was wondering if XFS was still working -- even with its
last on-disk structure changes -- and it _suprisingly_ worked as
expected. Right, now I can finally get rid of GRUB and use Syslinux to
boot my Linux on EFI from a rootfs with xfs. Shit, I have two
partitions (the first one being the required ESP) so there is no way to
access the other partitions since because Syslinux does not