search for: typecod

...> would lower the dynamic objects into the primitives the optimizers > already understand. Yep. I'm assuming that a language-specific optimizer would handle things like type inference, so the llvm code would either see plain primitives or a dynamic representation: struct object { int typecode; }; struct integer { int typecode; int value; }; Thus, the calling code could manipulate integers with pointers to objects. > If you can express the method dispatch in a way that is useful to the > preexisting optimizations, of course, you wouldn't have to do anything > special...

...31 @@ do_part_set_mbr_id (const char *device, int partnum, int idbyte) return 0; } + +int +do_part_set_gpt_type(const char *device, int partnum, const char *guid) +{ + if (partnum <= 0) { + reply_with_error ("partition number must be >= 1"); + return -1; + } + + char *typecode = NULL; + if (asprintf (&typecode, "%i:%s", partnum, guid) == -1) { + reply_with_perror ("asprintf"); + return -1; + } + + char *err = NULL; + int r = command (NULL, &err, str_sgdisk, device, "-t", typecode, NULL); + + if (r == -1) { + reply_with...

virt-resize didn't preserve the per-partition GPT GUID. Now that guests using UEFI are becoming common (basically it's the default on aarch64) we need to take into account that sometimes the partition GUID is used by the bootloader NVRAM variables to identify the boot partition, so it must be preserved across resize. This bug caused the 'virt-builder --size' option to fail on

How suitable do the developers think that LLVM would be as a code-generator for a dynamically typed langage? Would the lack of static type information make the traditional code optimizations performed by LLVM relatively ineffective? Sincerely, Rayiner Hashem

...s together with other > flags, it is pollute the common ELF code. If we factor out the > processing of MIPS specific flags, we have to duplicate code because a > symbol with say STO_MICROMIPS flag should be processed (setup size, > permissions etc) the same way as a regular DefinedAtom::typeCode > symbol. > > I considered to create a map symbol name => symbol flags, fill this > map while read object files, and use the map while write a linked > file. But I need to handle both local and global symbols and it is > possible to get symbols with the same name. > >...

STO_MIPS16 and STO_MICROMIPS flags denote that the symbol use a different "compressed" instructions encoding. Both these flags can be combined with usual "visibility" flags. It looks like adding new flag into the contentTypes set might solve the problem. Thanks for the idea. I try to implement it. On Thu, Nov 6, 2014 at 6:52 PM, Shankar Easwaran <shankare at

...r > > flags, it is pollute the common ELF code. If we factor out the > > processing of MIPS specific flags, we have to duplicate code because a > > symbol with say STO_MICROMIPS flag should be processed (setup size, > > permissions etc) the same way as a regular DefinedAtom::typeCode > > symbol. > > > > I considered to create a map symbol name => symbol flags, fill this > > map while read object files, and use the map while write a linked > > file. But I need to handle both local and global symbols and it is > > possible to get symbols wi...

...t;>> a) UnwindInfo >> If you are using dwarf unwind info, the dwarf FDE is just another atom (in .eh_frame section). We'll need a special reference in function atoms to their FDE atom, so that they get dead stripped or coalesced as a group (that is what ld64 does). > Do you mean typeCode atoms here ? Yes, eh frames are used in ELF. The eh_frame sections have to be first read to make this happen, so that function atoms may point to their respective FDE block. >>> b) LineInfo >> This was an experiment in ld64. At one point we thought it might be nice when erroring ou...

...om? That seems good to me. We just need to figure out >> what should happen with atoms not intended to be merged. Should the method >> assert? In the case where we want there to be a hash available, is it >> computed lazily? I was thinking that we could use this even for 'typeCode' atoms that could be merged if they have the same content too. This is a snip from a bug report for binutils ld :- <----snip---------> Identical code folding (icf) is currently implemented in GOLD. In our C++ applications it is very effective in reducing the size of libraries in pres...

...exists ("sgdisk"); } int @@ -619,10 +615,10 @@ do_part_set_gpt_type (const char *device, int partnum, const char *guid) CLEANUP_FREE char *err = NULL; int r = commandf (NULL, &err, COMMAND_FLAG_FOLD_STDOUT_ON_STDERR, - str_sgdisk, device, "-t", typecode, NULL); + "sgdisk", device, "-t", typecode, NULL); if (r == -1) { - reply_with_error ("%s %s -t %s: %s", str_sgdisk, device, typecode, err); + reply_with_error ("%s %s -t %s: %s", "sgdisk", device, typecode, err);...

....4/bin/mongrel_rails:97:in `run'' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/mongrel/command.rb:163:in`run'' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/bin/mongrel_rails:194 /usr/bin/mongrel_rails:18 Thread #<Thread:0xb7964a30 sleep> is too old, killing. brandcode: A1, typecode: A (From the production log) Processing Base#index (for 10.1.0.119 at 2006-06-19 15:40:07) [GET] Session ID: d1b4e8b6a073c9bd89c75a52563a017a Parameters: {} Mongrel::StopServer (Timed out thread.): /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/mongrel.rb:472:in`write'' /usr/...

...c data type name-Id mapping struct * and initialize the RS_dataTypeTable[]. Each driver could * define similar table for generating friendly type names */ struct data_types { char *typeName; Sint typeId; }; /* return the primitive type name for a primitive type id */ char *RS_DBI_getTypeName(Sint typeCode, const struct data_types table[]); /* same, but callable from S/R and vectorized */ s_object *RS_DBI_SclassNames(s_object *types); s_object *RS_DBI_createNamedList(char **names, Stype *types, Sint *lengths, Sint n); s_object *RS_DBI_copyFields(RS_DBI_fields *flds); void RS_na_set(void *ptr, Styp...

...exists ("sgdisk"); } int @@ -619,10 +617,10 @@ do_part_set_gpt_type (const char *device, int partnum, const char *guid) CLEANUP_FREE char *err = NULL; int r = commandf (NULL, &err, COMMAND_FLAG_FOLD_STDOUT_ON_STDERR, - str_sgdisk, device, "-t", typecode, NULL); + "sgdisk", device, "-t", typecode, NULL); if (r == -1) { - reply_with_error ("%s %s -t %s: %s", str_sgdisk, device, typecode, err); + reply_with_error ("%s %s -t %s: %s", "sgdisk", device, typecode, err);...

On Tue, May 7, 2013 at 10:08 PM, Nick Kledzik <kledzik at apple.com> wrote: > Shankar, > > Do you mean add a method like: > > virtual unsigned contentHash() const = 0; > > or maybe: > > virtual llvm::hash_code contentHash() const = 0 > > to lld::DefinedAtom? That seems good to me. We just need to figure out > what should happen with atoms not

...naryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) at System.Resources.ResourceReader.DeserializeObject(Int32 typeIndex) at System.Resources.ResourceReader.LoadObjectV2(Int32 pos, ResourceTypeCode& typeCode) at System.Resources.ResourceReader.LoadObject(Int32 pos) at System.Resources.ResourceReader.ResourceEnumerator.get_Entry() at System.Resources.ResourceReader.ResourceEnumerator.get_Current() at System.ComponentModel.ComponentResourceManager.FillResources(CultureInfo cult...

This is a simpler patch that removes GUESTFSD_EXT_CMD completely.

Replace GUESTFSD_EXT_CMD with a command line option ‘./guestfsd --print-external-commands’