similar to: size_t ndest_constraints = 0i in ssh-add.c

Hi! > RCS file: /home/cvs/dovecot/src/lib-index/mail-index.c,v > Working file: src/lib-index/mail-index.c > revision 1.268 > date: 2007-03-11 16:10:42 +0000; author: tss; state: Exp; lines: > > +8 -5; commitid: yo3GJUvm1yKgLG9s; > If we run out of disk space, move to in-memory indexes. I just saw the commit. Is this a "solution" for the Quota/FS problem, the

https://bugzilla.mindrot.org/show_bug.cgi?id=2287 Bug ID: 2287 Summary: AuthorizedKeysCommandUser should have it's default documented Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component:

Dear Security Team, I have prepared a new upload addressing a number of open security issues in Xen. Due to the complexity of the patches that address XSA-273 [0] the packages have been built from upstream's staging-4.8 / staging-4.10 branch again as recommended in that advisory. Commits on those branches are restricted to those that address the following XSAs (cf. [1]): - XSA-273

https://bugzilla.mindrot.org/show_bug.cgi?id=2501 Bug ID: 2501 Summary: VerifyHostKeyDNS & StrictHostKeyChecking Product: Portable OpenSSH Version: 7.1p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org

> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. Unfortunately, this requires manual grafting, since git-svn does really bad job here. I'm going to work on this tonight. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Dear Mailing List, What does this error mean and how do I fix it? I am on a Centos 4.9 >From /var/log/maillog : Jan 14 11:54:51 hostname imap(username): file lib.c: line 37 (nearest_power): assertion failed: (num <= ((size_t)1 << (BITS_IN_SIZE_T-1))) Version information : root at hostname[/etc/rc.d/rc3.d]# dovecot --version ; dovecot -n ; cat /etc/*release* 0.99.11 Usage:

This patch protects against redefinitions of size_t. There are currently at least two different definitions provided with klibc: unistd.h -> stddef.h -> bits32/bitsize/stddef.h sys/times.h -> linux/times.h -> linux/types.h both define size_t, causing gcc to complain. I suspect ptrdiff_t has a similar problem; not covered by this patch. Regards, Erik diff -urN

The return value from count_strings can only ever be >= 0, so it should be a size_t not an int. This is in preparation for fixing 598309, but I'm still testing that (rather large) patch. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats,

When reading this thread it occured to me that one could reserve i0 as an integer type that is semantically identical to iN where N is the size of (i8*) in bits. But on the other hand I just woke up, so this might be a silly idea :-) Cheers, Gabor

On Wed, 2008-05-07 at 14:25 -0700, Chris Lattner wrote: > On Wed, 7 May 2008, Jonathan S. Shapiro wrote: > > >> On Wed, 2008-05-07 at 13:24 -0700, Chris Lattner wrote: > >> Querying TargetData only works if you know the size of the pointer. :) > > > In the end, the use case that concerns me is things like character > > vectors, because of the fact that the

On Wed, 7 May 2008, Jonathan S. Shapiro wrote: >> >> i64 should be big enough for this. Just use i64. > > On a 32-bit platform, doesn't one want to use i32? Why? What is wrong with i64? -Chris -- http://nondot.org/sabre/ http://llvm.org/

On Wed, 7 May 2008, Jonathan S. Shapiro wrote: > On Wed, 2008-05-07 at 16:09 -0700, Chris Lattner wrote: >> On Wed, 7 May 2008, Jonathan S. Shapiro wrote: >>>> >>>> i64 should be big enough for this. Just use i64. >>> >>> On a 32-bit platform, doesn't one want to use i32? >> >> Why? What is wrong with i64? > > On its face,

On 2008-05-21, at 22:17, Talin wrote: > Chris Lattner wrote: >> On Wed, 21 May 2008, Talin wrote: >> >>> On a related topic: The source-level debugging descriptors require >>> you >>> to know up front what the sizeof pointer types are. Is there any >>> hope of >>> the frontend remaining blissfully unaware of platform details?

On May 22, 2008, at 6:40 PM, Talin wrote: >> LLVM already does this. >> >> http://www.nondot.org/sabre/LLVMNotes/SizeOf-OffsetOf-VariableSizedStructs.txt >> >> — Gordon >> > Is there a similar technique that would allow calculation of the > alignment? (which is also required by the DWARF derived-type > descriptor.) There is more than one form of

FWIW, SmallVector.h is part of LLVM, and so should be discussed on that mailing list. Leaving cfe-dev on the line so those who saw the initial mail can follow along. On Mon, Jun 4, 2012 at 2:14 PM, Will Wilson <will at indefiant.com> wrote: > Hi All, > > Just a quick question regarding SmallVector.h: It seems the interfaces > use a mixture of size_t, size_type and unsigned.

On Mon, Sep 23, 2019 at 03:46:41PM +0800, wangxu wrote: > From: Wang Xu <wangxu72 at huawei.com> > > Caller of vhost_exceeds_weight(..., total_len) in drivers/vhost/net.c > usually pass size_t total_len, which may be affected by rx/tx package. > > Signed-off-by: Wang Xu <wangxu72 at huawei.com> Puts a bit more pressure on the register file ... why do we care? Is

On 9/29/20 6:46 AM, Richard W.M. Jones wrote: > --- > generator/API.ml | 1 + > generator/API.mli | 1 + > generator/C.ml | 14 ++++++++++---- > generator/GoLang.ml | 5 +++++ > generator/OCaml.ml | 5 +++++ > generator/Python.ml | 11 +++++++++-- > 6 files changed, 31 insertions(+), 6 deletions(-) Looks good, and I'll push a counterpart patch adding

On Wed, 2008-05-07 at 16:09 -0700, Chris Lattner wrote: > On Wed, 7 May 2008, Jonathan S. Shapiro wrote: > >> > >> i64 should be big enough for this. Just use i64. > > > > On a 32-bit platform, doesn't one want to use i32? > > Why? What is wrong with i64? On its face, the problem is that it doesn't fit in a native register... or is there something

On Wed, 7 May 2008, Jonathan S. Shapiro wrote: >> On Wed, 2008-05-07 at 13:24 -0700, Chris Lattner wrote: >> Querying TargetData only works if you know the size of the pointer. :) > In the end, the use case that concerns me is things like character > vectors, because of the fact that the index spans depend on the address > space size. I'm not clear whether it is a goal

Gordon Henriksen wrote: > On 2008-05-21, at 22:17, Talin wrote: > >> As I understand this, this issue and others like it all require a >> difficult step to be taken, which is to introduce the concept of a >> constant whose value is not known until code generation time or at >> least >> until the compilation target is fully known. These "late bound