Displaying 9 results from an estimated 9 matches for "nptrs".
Did you mean:
ptrs
2011 Apr 05
0
[LLVMdev] Transition C->bitcode->assembly->object looses frame pointers
...-pointer bt.S -o bt-llc
$ ./bt-llc 4
backtrace() returned 1 addresses
./bt-llc() [0x4007f0]
$ cat bt.c
#include <execinfo.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
void
myfunc3(void)
{
int j, nptrs;
#define SIZE 100
void *buffer[100];
char **strings;
nptrs = backtrace(buffer, SIZE);
printf("backtrace() returned %d addresses\n", nptrs);
/* The call backtrace_symbols_fd(buffer, nptrs, STDOUT_FILENO)
would pr...
2011 Apr 05
3
[LLVMdev] Transition C->bitcode->assembly->object looses frame pointers
Hi James,
We've indeed passed the appropriate (and even excessive) flags to the
appropriate pipeline parts, that is:
llvm-gcc -O1 -fno-omit-frame-pointers -g $in -emit-llvm -S -o $name.ll
llc --disable-fp-elim $name.ll -o $name.S
g++ -fno-omit-frame-pointers -c $name.S
, but that didn't work
Alex
On Tue, Apr 5, 2011 at 4:40 PM, James Molloy <James.Molloy at arm.com> wrote:
2012 Aug 02
0
[PATCH 1/3] ALPHA: make sector size dynamic in extlinux
..._installed(int dev_fd);
#endif
diff --git a/libinstaller/syslxmod.c b/libinstaller/syslxmod.c
index c706f2c..be101f9 100644
--- a/libinstaller/syslxmod.c
+++ b/libinstaller/syslxmod.c
@@ -31,7 +31,8 @@
* Generate sector extents
*/
static void generate_extents(struct syslinux_extent *ex, int nptrs,
- const sector_t *sectp, int nsect)
+ const sector_t *sectp, int nsect,
+ unsigned sector_size)
{
uint32_t addr = 0x8000; /* ldlinux.sys starts loading here */
uint32_t base;
@@ -47,7 +48,7 @@ static void generate_extents(struct syslinux_extent *ex, int nptrs,
sec...
2004 Dec 09
1
Exim4 authentication patch
...k *ob =
+ (auth_dovecot_options_block *)(ablock->options_block);
+
+ if (ablock->public_name == NULL)
+ ablock->public_name = ablock->name;
+ if (ob->server_socket != NULL)
+ ablock->server = TRUE;
+ ablock->client = FALSE;
+}
+
+static int strcut(char *str, char **ptrs, int nptrs)
+{
+ char *tmp = str;
+ int n;
+
+ for (n = 0; n < nptrs; n++)
+ ptrs[n] = NULL;
+ n = 1;
+
+ while (*str) {
+ if (*str == '\t') {
+ if (n <= nptrs) {
+ *ptrs++ = tmp;
+ tmp = str + 1;
+ *str = 0;
+ }
+ n++;
+ }
+ str++;
+ }
+
+ if (n < nptrs)
+ *ptrs = tmp;
+...
2016 Feb 24
2
[PATCH 3/5] installers: MSVC compatibility fixes
More MSVC compatibility fixes, for packed structures.
NB: In case you are aware of the issues that may come with MS vs GCC
packing, so far, I have not seen evidence of detrimental impact from
using ms_struct packing in MSVC (vs gcc_struct, which is explicitly
specified for MinGW), with regards to the sections of code I am using in
Rufus.
-------------- next part --------------
2016 Mar 06
0
[PATCH 3/5] installers: MSVC compatibility fixes
...tions(+), 2 deletions(-)
>
> diff --git a/libinstaller/syslxmod.c b/libinstaller/syslxmod.c
> index 0ec4164..7bf4d91 100644
> --- a/libinstaller/syslxmod.c
> +++ b/libinstaller/syslxmod.c
> @@ -41,7 +41,8 @@ static void generate_extents(struct syslinux_extent _slimg
> *ex, int nptrs,
> unsigned int len;
>
> base = addr;
> - len = lba = 0;
> + len = 0;
> + lba = 0;
>
> memset_sl(ex, 0, nptrs * sizeof *ex);
Did Visual Studio actually complain about this one?
--
-Gene
2012 Sep 10
19
Initial support for sector size >512
This set of patches add some support for sector size >512.
Currently it fixes extlinux, MBR for GPT and ext partitions.
Other code is unaffected.
This set of patches has been tested on a read Dell machine running a beta
firmware.
2016 Mar 06
0
[PATCH 3/5] installers: MSVC compatibility fixes
On 3/6/2016 10:47, Pete Batard via Syslinux wrote:
> On 3/6/2016 08:13, Gene Cumm via Syslinux wrote:
>>> - len = lba = 0;
>>> >+ len = 0;
>>> >+ lba = 0;
>>> >
>>> > memset_sl(ex, 0, nptrs * sizeof *ex);
>> Did Visual Studio actually complain about this one?
>
> WDK compiler (which I also use) if I recall correctly. At any rate,
> some older compilers do not like double initializations like this one,
> and I don't think this change should be much of a contenti...
2016 Mar 06
2
[PATCH 3/5] installers: MSVC compatibility fixes
On 2016.03.06 13:13, Gene Cumm wrote:
> Did Visual Studio actually complain about this one?
WDK compiler (which I also use) if I recall correctly. At any rate, some
older compilers do not like double initializations like this one, and I
don't think this change should be much of a contention point, since it
doesn't introduce any liability.
Regards,
/Pete