Displaying 17 results from an estimated 17 matches for "elf64_half".
2019 Apr 30
3
RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler
...st_name;
Elf32_Addr st_value;
Elf32_Word st_size;
unsigned char st_info;
unsigned char st_other;
Elf32_Half st_shndx;
} Elf32_Sym;
typedef struct {
Elf64_Word st_name;
unsigned char st_info;
unsigned char st_other;
Elf64_Half st_shndx;
Elf64_Addr st_value;
Elf64_Xword st_size;
} Elf64_Sym;
The st_size and st_value fields could be used to represent attribute information about a given symbol:
* The st_size field can be split into an attribute ID and a symbol index for the symbol that the at...
2005 Jan 06
0
[PATCH] ELF headers
...6 +7,10 @@
#include <sys/elfcommon.h>
+#define ELF64_ST_BIND(val) ST_BIND (val)
+#define ELF64_ST_TYPE(val) ST_TYPE (val)
+#define ELF64_ST_INFO(bind, type) ST_INFO ((bind), (type))
+
/* ELF standard typedefs (yet more proof that <stdint.h> was way overdue) */
typedef uint16_t Elf64_Half;
typedef int16_t Elf64_SHalf;
diff -uNr klibc-0.178/include/sys/elfcommon.h klibc-0.178-fogo/include/sys/elfcommon.h
--- klibc-0.178/include/sys/elfcommon.h 2004-01-30 14:40:51.000000000 -0700
+++ klibc-0.178-fogo/include/sys/elfcommon.h 2004-09-20 09:21:09.000000000 -0600
@@ -2,6 +2,8 @@
* sy...
2019 Apr 30
3
[EXTERNAL] Re: RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler
...char st_info;
>
> unsigned char st_other;
>
> Elf32_Half st_shndx;
>
> } Elf32_Sym;
>
>
>
> typedef struct {
>
> Elf64_Word st_name;
>
> unsigned char st_info;
>
> unsigned char st_other;
>
> Elf64_Half st_shndx;
>
> Elf64_Addr st_value;
>
> Elf64_Xword st_size;
>
> } Elf64_Sym;
>
>
>
> The st_size and st_value fields could be used to represent attribute information about a given symbol:
>
>
>
> The st_size field can be split into...
2019 May 01
2
RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler
...;
> Elf32_Half st_shndx;
>
> } Elf32_Sym;
>
>
>
> typedef struct {
>
> Elf64_Word st_name;
>
> unsigned char st_info;
>
> unsigned char st_other;
>
> Elf64_Half st_shndx;
>
> Elf64_Addr st_value;
>
> Elf64_Xword st_size;
>
> } Elf64_Sym;
>
>
>
> The st_size and st_value fields could be used to represent attribute information about a given symbol:
>
>...
2007 Jun 01
2
another RFC patch: bzImage with ELF payload
...4_Addr st_value; /* Value of the symbol */
Elf64_Xword st_size; /* Associated symbol size */
};
-
+#endif /* __ASSEMBLY__ */
#define EI_NIDENT 16
+#ifndef __ASSEMBLY__
struct elf32_hdr {
unsigned char e_ident[EI_NIDENT];
Elf32_Half e_type;
@@ -223,6 +229,7 @@ struct elf64_hdr {
Elf64_Half e_shnum;
Elf64_Half e_shstrndx;
};
+#endif /* __ASSEMBLY__ */
/* These constants define the permissions on sections in the program
header, p_flags. */
@@ -230,6 +237,7 @@ struct elf64_hdr {
#define PF_W 0x2
#define PF_X 0x1
+#ifndef __ASSEMBLY__
struct elf32_phdr {
Elf32_Word p...
2007 Jun 01
2
another RFC patch: bzImage with ELF payload
...4_Addr st_value; /* Value of the symbol */
Elf64_Xword st_size; /* Associated symbol size */
};
-
+#endif /* __ASSEMBLY__ */
#define EI_NIDENT 16
+#ifndef __ASSEMBLY__
struct elf32_hdr {
unsigned char e_ident[EI_NIDENT];
Elf32_Half e_type;
@@ -223,6 +229,7 @@ struct elf64_hdr {
Elf64_Half e_shnum;
Elf64_Half e_shstrndx;
};
+#endif /* __ASSEMBLY__ */
/* These constants define the permissions on sections in the program
header, p_flags. */
@@ -230,6 +237,7 @@ struct elf64_hdr {
#define PF_W 0x2
#define PF_X 0x1
+#ifndef __ASSEMBLY__
struct elf32_phdr {
Elf32_Word p...
2007 May 31
1
[patch rfc wip] first cut of ELF bzImage
...e of the symbol */
Elf64_Xword st_size; /* Associated symbol size */
} Elf64_Sym;
-
+#endif /* __ASSEMBLY__ */
#define EI_NIDENT 16
+#ifndef __ASSEMBLY__
typedef struct elf32_hdr{
unsigned char e_ident[EI_NIDENT];
Elf32_Half e_type;
@@ -222,6 +228,7 @@ typedef struct elf64_hdr {
Elf64_Half e_shnum;
Elf64_Half e_shstrndx;
} Elf64_Ehdr;
+#endif /* __ASSEMBLY__ */
/* These constants define the permissions on sections in the program
header, p_flags. */
@@ -229,6 +236,7 @@ typedef struct elf64_hdr {
#define PF_W 0x2
#define PF_X 0x1
+#ifndef __ASSEMBLY__
typedef struct e...
2007 May 31
1
[patch rfc wip] first cut of ELF bzImage
...e of the symbol */
Elf64_Xword st_size; /* Associated symbol size */
} Elf64_Sym;
-
+#endif /* __ASSEMBLY__ */
#define EI_NIDENT 16
+#ifndef __ASSEMBLY__
typedef struct elf32_hdr{
unsigned char e_ident[EI_NIDENT];
Elf32_Half e_type;
@@ -222,6 +228,7 @@ typedef struct elf64_hdr {
Elf64_Half e_shnum;
Elf64_Half e_shstrndx;
} Elf64_Ehdr;
+#endif /* __ASSEMBLY__ */
/* These constants define the permissions on sections in the program
header, p_flags. */
@@ -229,6 +236,7 @@ typedef struct elf64_hdr {
#define PF_W 0x2
#define PF_X 0x1
+#ifndef __ASSEMBLY__
typedef struct e...
2019 May 01
4
RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler
...; >
> > > typedef struct {
> > >
> > > Elf64_Word st_name;
> > >
> > > unsigned char st_info;
> > >
> > > unsigned char st_other;
> > >
> > > Elf64_Half st_shndx;
> > >
> > > Elf64_Addr st_value;
> > >
> > > Elf64_Xword st_size;
> > >
> > > } Elf64_Sym;
> > >
> > >
> > >
> > > The st_size and st_...
2019 May 06
2
[EXTERNAL] Re: RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler
...; >
> > > typedef struct {
> > >
> > > Elf64_Word st_name;
> > >
> > > unsigned char st_info;
> > >
> > > unsigned char st_other;
> > >
> > > Elf64_Half st_shndx;
> > >
> > > Elf64_Addr st_value;
> > >
> > > Elf64_Xword st_size;
> > >
> > > } Elf64_Sym;
> > >
> > >
> > >
> > > The st_size and st_...
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over boot_params.setup_sects worth
of 16-bit setup code.
4. Update the boot_params to 2.07, and update the
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over boot_params.setup_sects worth
of 16-bit setup code.
4. Update the boot_params to 2.07, and update the
2019 May 07
2
[EXTERNAL] Re: RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler
...t;
>> > > > Elf64_Word st_name;
>> > > >
>> > > > unsigned char st_info;
>> > > >
>> > > > unsigned char st_other;
>> > > >
>> > > > Elf64_Half st_shndx;
>> > > >
>> > > > Elf64_Addr st_value;
>> > > >
>> > > > Elf64_Xword st_size;
>> > > >
>> > > > } Elf64_Sym;
>> > > >
>> >...
2019 May 09
3
[EXTERNAL] Re: RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler
...ruct {
> > > >
> > > > Elf64_Word st_name;
> > > >
> > > > unsigned char st_info;
> > > >
> > > > unsigned char st_other;
> > > >
> > > > Elf64_Half st_shndx;
> > > >
> > > > Elf64_Addr st_value;
> > > >
> > > > Elf64_Xword st_size;
> > > >
> > > > } Elf64_Sym;
> > > >
> > > >
> > >...
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some