On 09.04.2017 13:32, Bruce Evans wrote:
> How do you initialize actual use of sc->cursor_char? It is only used
> when SC_NO_FONT_LOADING is not defined. Configuring SC_PIXEL_MODE
> forces SC_NO_FONT_LOADING to be undefined. Except to test sc->cursor_char,
I use text console mode with loading
On 09.04.2017 10:33, Bruce Evans wrote:
> On Sun, 9 Apr 2017, Andrey Chernov wrote:
>
>> On 09.04.2017 7:54, Andrey Chernov wrote:
>>> On 08.04.2017 13:00, Bruce Evans wrote:
>>>> Log:
>>>> Quick fix for removal of the mouse cursor in vga direct grap
On 09.04.2017 9:46, Bruce Evans wrote:
>> Please don't forget that this 5 cells range (0xd0-0xd4, last one becomes
>> SC_CURSOR_CHAR) can be redefined with "vidcontrol -M", it is needed for
>> the case they overlap valid characters region for some code tables.
>
> I didn't forget it, but these
On 09.04.2017 7:54, Andrey Chernov wrote:
> On 08.04.2017 13:00, Bruce Evans wrote:
>> Log:
>> Quick fix for removal of the mouse cursor in vga direct graphics modes
>> (that is, in all supported 8, 15, 16 and 24-color modes). Moving the
>> mouse cursor while ho
On 08.04.2017 13:00, Bruce Evans wrote:
> Log:
> Quick fix for removal of the mouse cursor in vga direct graphics modes
> (that is, in all supported 8, 15, 16 and 24-color modes). Moving the
> mouse cursor while holding down a button (giving cut marking) left a
> trail of garbage from
On 04.04.2017 16:41, Kyle Evans wrote:
> Upon further review, newer versions of GNU grep(1) drop the explicit
> '00' and add the \33[K dropped in this commit a few lines above the
> mentioned one. In that case, we might as well revert those two lines and
> consider this an improvement. I guess it
On 04.04.2017 16:05, Bruce Evans wrote:
> This might be to work around a bug in a terminal driver. I needed the
> 0 (but just one) to reset the attributes in my attribute tests, on at
> least 1 of the tested terminals (current sc, current vt, old sc, old
> xterm, old cygwin xterm). CSI m seems
33[00m as defined by ANSI.
Of course we must handle (and already handle) both according to ANSI,
but few CPU cycles here, then in another place, yet another, etc. making
big time in sum when CPU does nothing useful but resource eating.
> On Tue, Apr 4, 2017 at 7:37 AM, Andrey Chernov <a...@freebsd
On 04.04.2017 15:24, Kyle Evans wrote:
> On Tue, Apr 4, 2017 at 7:07 AM, Andrey Chernov <a...@freebsd.org
> <mailto:a...@freebsd.org>> wrote:
>
> On 04.04.2017 2:16, Ed Maste wrote:
> > if (color)
> > -
On 04.04.2017 2:16, Ed Maste wrote:
> if (color)
> - fprintf(stdout, "\33[m\33[K");
> + fprintf(stdout, "\33[00m\33[K");
Please back that one out. We don't need to handle internally or print
remotely excessive 00.
At
On 23.12.2016 1:39, Conrad Meyer wrote:
> This was unjustified and inappropriate.
I don't think so. While being able to back it out or fix it by another
way by yourself, you just doing nothing for several days. Your personal
reasons of inability to act properly so long time weights less than
On 19.09.2016 19:13, Conrad E. Meyer wrote:
> + /*
> + * Cache NLS data, for strerror, for err(3), before entering capability
> + * mode.
> + */
> + (void)catopen("libc", NL_CAT_LOCALE);
This code should be common for all programs which use err(), perror()
etc. since they
On 29.08.2016 22:10, Konstantin Belousov wrote:
> On Mon, Aug 29, 2016 at 09:16:29PM +0300, Andrey Chernov wrote:
>> Previous text is documented everywhere and describing usual good
>> practice, so it should remains in place, in that means r304928 should be
>> reverted, becau
On 29.08.2016 21:16, Andrey Chernov wrote:
> On 29.08.2016 21:04, Konstantin Belousov wrote:
>> On Mon, Aug 29, 2016 at 08:46:47PM +0300, Andrey Chernov wrote:
>>> Either we implement this wrapper or left all things as is, we need to
>>> document internal errno clearin
On 29.08.2016 21:04, Konstantin Belousov wrote:
> On Mon, Aug 29, 2016 at 08:46:47PM +0300, Andrey Chernov wrote:
>> Either we implement this wrapper or left all things as is, we need to
>> document internal errno clearing additionally, to not make people wonder
>> why errn
On 29.08.2016 19:51, John Baldwin wrote:
>> int
>> ptrace(int request, pid_t pid, caddr_t addr, int data)
>> {
>>
>> errno = 0;
>> return (__sys_ptrace(request, pid, addr, data));
>> }
>
> Certainly I think having a C wrapper like this makes more sense than
> doing it all in assembly N
On 29.08.2016 18:34, Konstantin Belousov wrote:
> On Mon, Aug 29, 2016 at 06:05:50PM +0300, Andrey Chernov wrote:
>> No surprise since they all share the same initial implementation. You
>> can add NetBSD and OpenBSD too. Errno clearing as undocumented side
>> effect is not wh
On 29.08.2016 10:07, Konstantin Belousov wrote:
> On Mon, Aug 29, 2016 at 09:58:13AM +0300, Konstantin Belousov wrote:
>> On Sun, Aug 28, 2016 at 04:09:51PM -0700, John Baldwin wrote:
>>> OTOH, given that we explicitly documented it as not being true, I suspect
>>> any applications that are using
On 28.08.2016 8:28, Bruce Evans wrote:
>> How hard it will be to bring ptrace() to what C99 expects? Perhaps now
>> time is suited well to change some obsoleted things.
>
> This should be safe to change, since portable applications like gdb can't
> assume that the implemementation clobbers errno
On 28.08.2016 5:33, Andrey Chernov wrote:
> "conforming implementation may have extensions (including additional
> library functions), provided they do not alter the behavior of any
> strictly conforming program.3)"
>
> ptrace() is extension (additional library function)
On 28.08.2016 4:52, Konstantin Belousov wrote:
POSIX: "For each thread of a process, the value of errno shall not be
affected by function calls or assignments to errno by other threads."
>>> And ? What should the citation add new to the substance
>>> of the code change ?
>>
>> This is
On 28.08.2016 4:37, Andrey Chernov wrote:
> On 28.08.2016 4:25, Andrey Chernov wrote:
>>> Point me to a single line in C99 which mentions ptrace().
>
> Already done: ptrace == "any library function".
To elaborate it more, C99 does not have finite list of library
On 28.08.2016 4:25, Andrey Chernov wrote:
>> Point me to a single line in C99 which mentions ptrace().
Already done: ptrace == "any library function".
___
svn-src-head@freebsd.org mailing list
https://lists.freebsd.org/mailman/listi
On 28.08.2016 4:15, Konstantin Belousov wrote:
>> POSIX: "No function in this volume of POSIX.1-2008 shall set errno to zero."
> I am quite curious where ptrace(2) is defined by POSIX.
POSIX just repeats C99 statement for its own functions, supporting this
rule too, but C99 rule is more general
On 28.08.2016 4:04, Andrey Chernov wrote:
> On 28.08.2016 3:56, Konstantin Belousov wrote:
>> On Sun, Aug 28, 2016 at 03:38:10AM +0300, Andrey Chernov wrote:
>>> On 28.08.2016 2:03, Konstantin Belousov wrote:
>>>> Since ptrace(2) syscall can return -1
On 28.08.2016 3:56, Konstantin Belousov wrote:
> On Sun, Aug 28, 2016 at 03:38:10AM +0300, Andrey Chernov wrote:
>> On 28.08.2016 2:03, Konstantin Belousov wrote:
>>> Since ptrace(2) syscall can return -1 for non-error situations, libc
>>> wrappers set errno to 0 be
On 28.08.2016 3:38, Andrey Chernov wrote:
> On 28.08.2016 2:03, Konstantin Belousov wrote:
>> Since ptrace(2) syscall can return -1 for non-error situations, libc
>> wrappers set errno to 0 before performing the syscall, as the service
>> to the caller.
>
>
On 28.08.2016 2:03, Konstantin Belousov wrote:
> Since ptrace(2) syscall can return -1 for non-error situations, libc
> wrappers set errno to 0 before performing the syscall, as the service
> to the caller.
Both C99 and POSIX directly prohibits any standard function to set errno
to 0.
On 27.08.2016 20:37, Brooks Davis wrote:
> On Sat, Aug 27, 2016 at 02:43:13PM +, Andrey A. Chernov wrote:
>> Author: ache
>> Date: Sat Aug 27 14:43:13 2016
>> New Revision: 304911
>> URL: https://svnweb.freebsd.org/changeset/base/304911
>>
>> Log:
>> The formal behavior of qsort is unstable
On 25.08.2016 5:58, Cy Schubert wrote:
> Author: cy
> Date: Thu Aug 25 02:58:41 2016
> New Revision: 304781
> URL: https://svnweb.freebsd.org/changeset/base/304781
>
> Log:
> Add logic to replace the working ntp leap-seconds file in /var/db
> if it contains a $FreeBSD$ header. The header will
On 23.08.2016 23:53, Ngie Cooper (yaneurabeya) wrote:
>
>> On Aug 23, 2016, at 13:33, Andrey A. Chernov wrote:
>>
>> Author: ache
>> Date: Tue Aug 23 20:33:56 2016
>> New Revision: 304703
>> URL: https://svnweb.freebsd.org/changeset/base/304703
>>
>> Log:
>> LC_*_MASK bit
On 08.08.2016 1:48, Xin Li wrote:
> Well, despite the fact that I have to admit that I get locked out from
> my own storage box too, however (even without wearing any hat) I am for
> the change and would blame myself for being lazy in adopting the change
> when the upstream have announced it
On 08.08.2016 0:28, Andrey Chernov wrote:
> On 08.08.2016 0:20, Warner Losh wrote:
>>
>>> On Aug 7, 2016, at 3:11 PM, Andrey Chernov <a...@freebsd.org> wrote:
>>>
>>>> OTOH, FreeBSD has a documented deprecation process that says things will
>>
On 08.08.2016 0:20, Warner Losh wrote:
>
>> On Aug 7, 2016, at 3:11 PM, Andrey Chernov <a...@freebsd.org> wrote:
>>
>>> OTOH, FreeBSD has a documented deprecation process that says things will
>>> continue working for a major release after bein
On 07.08.2016 22:56, Slawa Olhovchenkov wrote:
> On Sun, Aug 07, 2016 at 10:42:56PM +0300, Andrey Chernov wrote:
>
>> On 07.08.2016 22:10, Slawa Olhovchenkov wrote:
>>> On Sun, Aug 07, 2016 at 10:02:52PM +0300, Andrey Chernov wrote:
>>>
>>>> On
On 07.08.2016 22:10, Slawa Olhovchenkov wrote:
> On Sun, Aug 07, 2016 at 10:02:52PM +0300, Andrey Chernov wrote:
>
>> On 07.08.2016 21:52, Slawa Olhovchenkov wrote:
>>>> Why you still not
>>>> send your opinion to the author?
>>>>
>>>
>
On 07.08.2016 21:52, Slawa Olhovchenkov wrote:
>> Why you still not
>> send your opinion to the author?
>>
>
> I am not sure about suitable response from autor.
> May be project [FreeBSD] choise some compromise.
IMHO blindly choosing some compromise without asking author's opinion
first will be
On 07.08.2016 21:23, Slawa Olhovchenkov wrote:
> On Sun, Aug 07, 2016 at 09:06:37PM +0300, Andrey Chernov wrote:
>
>> On 07.08.2016 20:43, Andrey Chernov wrote:
>>> On 07.08.2016 20:37, Slawa Olhovchenkov wrote:
>>>> On Sun, Aug 07, 2016 at 08:34
On 07.08.2016 20:43, Andrey Chernov wrote:
> On 07.08.2016 20:37, Slawa Olhovchenkov wrote:
>> On Sun, Aug 07, 2016 at 08:34:55PM +0300, Andrey Chernov wrote:
>>
>>> On 07.08.2016 20:31, Andrey Chernov wrote:
>>>> On 07.08.2016 19:14, Bruce Simpson wrote:
>&g
On 07.08.2016 20:37, Slawa Olhovchenkov wrote:
> On Sun, Aug 07, 2016 at 08:34:55PM +0300, Andrey Chernov wrote:
>
>> On 07.08.2016 20:31, Andrey Chernov wrote:
>>> On 07.08.2016 19:14, Bruce Simpson wrote:
>>>> On 07/08/16 15:40, Warner Losh wrote:
>>>&g
On 07.08.2016 20:31, Andrey Chernov wrote:
> On 07.08.2016 19:14, Bruce Simpson wrote:
>> On 07/08/16 15:40, Warner Losh wrote:
>>> That’s a cop-out answer. We, as a project, need to articulate to our
>>> users, whom we care about, why this rather obnoxious hit
On 07.08.2016 19:14, Bruce Simpson wrote:
> On 07/08/16 15:40, Warner Losh wrote:
>> That’s a cop-out answer. We, as a project, need to articulate to our
>> users, whom we care about, why this rather obnoxious hit to usability
>> was taken. The answer must be more complete than “We just disabled
On 07.08.2016 20:31, Andrey Chernov wrote:
> On 07.08.2016 19:14, Bruce Simpson wrote:
>> On 07/08/16 15:40, Warner Losh wrote:
>>> That’s a cop-out answer. We, as a project, need to articulate to our
>>> users, whom we care about, why this rather obnoxious hit
On 07.08.2016 17:40, Warner Losh wrote:
>
>> On Aug 7, 2016, at 7:21 AM, Andrey Chernov <a...@freebsd.org> wrote:
>>>
>>>> We can't turn our security
>>>> team into compatibility team, by constantly restoring removed code, such
>>>>
On 07.08.2016 15:52, Slawa Olhovchenkov wrote:
>> You should address your complains to original openssh author instead, it
>> was his decision to get rid of weak algos. In my personal opinion, if
>> your hardware is outdated, just drop it out.
>
> Hardware outdated by outdated main function, not
On 07.08.2016 14:59, Bruce Simpson wrote:
> On 07/08/16 12:43, Oliver Pinter wrote:
>>> I was able to override this (somewhat unilateral, to my mind)
>>> deprecation of the DH key exchange by using this option:
>>> -oKexAlgorithms=+diffie-hellman-group1-sha1
>>
>> You can add this option to
On 02.08.2016 12:26, Gleb Smirnoff wrote:
> You got your own commit access now, so please do it yourself if you
> are confident enough about the change. I am not :)
Really this date is in the middle, see
http://bibliopskov.ru/4november.htm
___
On 30.07.2016 11:52, Bruce Evans wrote:
> On Sat, 30 Jul 2016, Andrey Chernov wrote:
>
>> On 30.07.2016 7:15, Bruce Evans wrote:
>>> On Sat, 30 Jul 2016, Andrey A. Chernov wrote:
>>>
>>>> Log:
>>>> Reset errno for readdirfunc() before contunu
On 30.07.2016 7:15, Bruce Evans wrote:
> On Sat, 30 Jul 2016, Andrey A. Chernov wrote:
>
>> Log:
>> Reset errno for readdirfunc() before contunue.
>
> In C99, library functions are not permitted to set errno to 0. The glob()
> family shouldn't use a different (worse) convention, and POSIX
On 27.07.2016 3:46, Kevin Lo wrote:
> Author: kevlo
> Date: Wed Jul 27 00:46:48 2016
> New Revision: 303354
> URL: https://svnweb.freebsd.org/changeset/base/303354
>
> Log:
> Add weekday to the date format.
This file is generated, so this change will be lost after next
generation. It will be
On 23.07.2016 15:32, Baptiste Daroussin wrote:
> On Sat, Jul 23, 2016 at 02:58:31PM +0300, Andrey Chernov wrote:
>> On 23.07.2016 14:52, Baptiste Daroussin wrote:
>>> On Sat, Jul 23, 2016 at 02:41:39PM +0300, Andrey Chernov wrote:
>>>> On 23.07.2016 14:24, Baptiste
What happens with the lines below?
On 24.07.2016 13:35, Gleb Smirnoff wrote:
> Modified: head/usr.bin/calendar/calendars/ru_RU.UTF-8/calendar.orthodox
> -Пасха-7 Вход Господень в Иерусалим. Вербное Воскресенье
> +Пасха-7 Вход Господень в Иерусалим. Вербное Воскресент.ье
> +Пасха
On 23.07.2016 14:52, Baptiste Daroussin wrote:
> On Sat, Jul 23, 2016 at 02:41:39PM +0300, Andrey Chernov wrote:
>> On 23.07.2016 14:24, Baptiste Daroussin wrote:
>>> Author: bapt
>>> Date: Sat Jul 23 11:24:05 2016
>>> New Revision: 303218
>>> URL: htt
On 23.07.2016 14:24, Baptiste Daroussin wrote:
> Author: bapt
> Date: Sat Jul 23 11:24:05 2016
> New Revision: 303218
> URL: https://svnweb.freebsd.org/changeset/base/303218
>
> Log:
> Add another hack to add weekday to date format to more locales
>
> While here only initialize the iconv
say so only. They are different entities
differently encoded and cross assigning between wchar_t and char is not
recommended.
>
> On 2016-Jul-11, at 8:57 PM, Andrey Chernov wrote:
>
>> On 12.07.2016 5:44, Mark Millard wrote:
>>> My understanding of the criteria f
On 12.07.2016 11:35, Andrew Turner wrote:
> On Tue, 12 Jul 2016 00:37:48 + (UTC)
> "Andrey A. Chernov" wrote:
>
>> Author: ache
>> Date: Tue Jul 12 00:37:48 2016
>> New Revision: 302601
>> URL: https://svnweb.freebsd.org/changeset/base/302601
>>
>> Log:
>> I don't know
On 12.07.2016 5:44, Mark Millard wrote:
> My understanding of the criteria for __WCHAR_MIN and __WCHAR_MAX:
>
> A) __WCHAR_MIN and __WCHAR_MAX: same type as the integer promotion of
> ___wchar_t (if that is distinct).
> B) __WCHAR_MIN is the low value for ___wchar_t as an integer type; not
>
On 21.06.2016 10:12, Baptiste Daroussin wrote:
> On Mon, Jun 20, 2016 at 10:14:04PM +0300, Andrey Chernov wrote:
>> On 20.06.2016 9:45, Baptiste Daroussin wrote:
>>> Author: bapt
>>> Date: Mon Jun 20 06:45:42 2016
>>> New Revision: 302026
>>> URL: htt
On 20.06.2016 9:45, Baptiste Daroussin wrote:
> Author: bapt
> Date: Mon Jun 20 06:45:42 2016
> New Revision: 302026
> URL: https://svnweb.freebsd.org/changeset/base/302026
>
> Log:
> Fix generation of locales with multiple variants
Thanx.
Just want to note, even if we stay with RFC 5646
On 19.06.2016 22:40, Baptiste Daroussin wrote:
> On Sun, Jun 19, 2016 at 10:02:26PM +0300, Andrey Chernov wrote:
>> On 19.06.2016 20:21, Andrey Chernov wrote:
>>> On 19.06.2016 20:10, Baptiste Daroussin wrote:
>>>> On Sun, Jun 19, 2016 at 08:05:30PM +0300, Andrey Cher
On 19.06.2016 20:21, Andrey Chernov wrote:
> On 19.06.2016 20:10, Baptiste Daroussin wrote:
>> On Sun, Jun 19, 2016 at 08:05:30PM +0300, Andrey Chernov wrote:
>>> On 19.06.2016 19:52, Andrey Chernov wrote:
>>>> On 19.06.2016 19:47, Andrey Chernov wrote:
>&
On 19.06.2016 20:10, Baptiste Daroussin wrote:
> On Sun, Jun 19, 2016 at 08:05:30PM +0300, Andrey Chernov wrote:
>> On 19.06.2016 19:52, Andrey Chernov wrote:
>>> On 19.06.2016 19:47, Andrey Chernov wrote:
>>>> On 19.06.2016 18:49, Baptiste Daroussin wrote:
>>&g
On 19.06.2016 20:05, Baptiste Daroussin wrote:
> On Sun, Jun 19, 2016 at 07:47:27PM +0300, Andrey Chernov wrote:
>> On 19.06.2016 18:49, Baptiste Daroussin wrote:
>>> On Sun, Jun 19, 2016 at 04:52:34PM +0200, Baptiste Daroussin wrote:
>>>> On Sun, Jun 19, 2016 at 07
On 19.06.2016 19:52, Andrey Chernov wrote:
> On 19.06.2016 19:47, Andrey Chernov wrote:
>> On 19.06.2016 18:49, Baptiste Daroussin wrote:
>>> On Sun, Jun 19, 2016 at 04:52:34PM +0200, Baptiste Daroussin wrote:
>>>> On Sun, Jun 19, 2016 at 07:57:49AM +0300, Andrey Cher
On 19.06.2016 19:47, Andrey Chernov wrote:
> On 19.06.2016 18:49, Baptiste Daroussin wrote:
>> On Sun, Jun 19, 2016 at 04:52:34PM +0200, Baptiste Daroussin wrote:
>>> On Sun, Jun 19, 2016 at 07:57:49AM +0300, Andrey Chernov wrote:
>>>> On 19.06.2016 6:44, H
On 19.06.2016 18:49, Baptiste Daroussin wrote:
> On Sun, Jun 19, 2016 at 04:52:34PM +0200, Baptiste Daroussin wrote:
>> On Sun, Jun 19, 2016 at 07:57:49AM +0300, Andrey Chernov wrote:
>>> On 19.06.2016 6:44, Hajimu UMEMOTO wrote:
>>>> Log:
>>>>
On 19.06.2016 8:31, Hajimu UMEMOTO wrote:
> Hi,
>
>>>>>> On Sun, 19 Jun 2016 07:57:49 +0300
>>>>>> Andrey Chernov <a...@freebsd.org> said:
>
> ache> Nonsense doubled formats in sr_*_RS locales and nonsense md_order there
> too.
>
On 19.06.2016 6:44, Hajimu UMEMOTO wrote:
> Log:
> - Prefer to use %d over %e where the day of the month should be zero
> filled.
> - Since %e means the day of the month as well, regard %e as same as %d
> in md_order.
Nonsense doubled formats in sr_*_RS locales and nonsense md_order
On 10.06.2016 17:14, Pedro Giffuni wrote:
>> Because now strcoll_l() is used as before and it is broken in wide char
>> converting process. It is broken for _all_, not just for vfscanf()
>> ranges. It should never fail with any args.
>> Real fix should be in strcoll_l().
>>
>
> Yes, it is broken
On 10.06.2016 15:03, Pedro Giffuni wrote:
> (Sorry I have been offline/sleep for a while)
>
> Hello;
>
> I cannot back this out because of this report:
>
> http://docs.freebsd.org/cgi/mid.cgi?20160608132224.GA15454
>
> This change only re-states what has been working before the ABI breakage
>
Please back it out. __sccl() use plain chars, you can't just call wide
chars __wcollate_range_cmp() from it. Never intermix plain chars and
wide chars without conversion. The problem is somewhere else. The code
used for [a-z] ranges in the format. Moreover, even if conversion added
this code can't
On 06.06.2016 20:52, Slawa Olhovchenkov wrote:
>> BTW, it is good idea: to check first, is supported firewall enabled, and
>> only then enable blacklistd by default.
>
> What purpose? SUDDENLY lockout access to own host after some mistake
> in password?
I agree that default 1 day locking is too
On 06.06.2016 20:22, Ian Lepore wrote:
> On Mon, 2016-06-06 at 20:06 +0300, Andrey Chernov wrote:
>> As variant, I keep hope blacklist sh helper will teach about ipfw
>> soon,
>> it looks possible. Then it can be re-enabled by default.
>
> No, it should still not be
On 06.06.2016 20:00, Ian Lepore wrote:
> Probably everyone assumed (like I did) that it would be disabled by
> default, and didn't notice that wasn't the case. Your response
> indicates the problem with "default enabled"... you mention enabling
> packet filtering in pf.conf, my response is: WTF
On 05.06.2016 22:12, Pedro F. Giffuni wrote:
> When collation support was brought in, the second and third
> arguments in __collate_range_cmp() were changed from int to
> wchar_t, breaking the ABI. Change them to a "char" type which
> makes more sense and keeps the ABI compatible.
Not
On 05.06.2016 22:12, Pedro F. Giffuni wrote:
> --- head/lib/libc/regex/regcomp.c Sun Jun 5 18:16:33 2016
> (r301460)
> +++ head/lib/libc/regex/regcomp.c Sun Jun 5 19:12:52 2016
> (r301461)
> @@ -821,10 +821,10 @@ p_b_term(struct parse *p, cset *cs)
>
On 03.06.2016 20:44, Bryan Drewery wrote:
> Thanks!
>
> I think this helps Andrey's recent clang rebuild issues as well since
> the quite-common file was being touched often.
Thanx!
>
> On 6/3/2016 9:17 AM, Dimitry Andric wrote:
>> Author: dim
>> Date: Fri Jun 3 16:17:36 2016
>> New Revision:
On 31.05.2016 17:17, Bruce Evans wrote:
> Our rand should use just 1, and it is dangerous to change RAND_MAX again,
> but can we even change the sequences? Something might depend on
> reproducing the old sequences.
This question already arises many times. The sequence must be
reproducible during
This implementation of shifts 32-bit and 64-bit PRNGs looks more
reliable than Mersenne primes and don't use Bignums:
http://wwwmaths.anu.edu.au/~brent/ftp/random/xorgens305.tar.gz
PDF article inside.
On 31.05.2016 14:30, Andrey Chernov wrote:
> On 31.05.2016 12:58, Bruce Evans wrote:
>&g
On 31.05.2016 12:58, Bruce Evans wrote:
> On Tue, 31 May 2016, Andrey Chernov wrote:
>
>> On 31.05.2016 9:48, Bruce Evans wrote:
>>>> Perhaps you can find some ideas, answers and PRNG comparison in the
>>>> original paper:
>>>> http://www.firstpr.c
On 31.05.2016 9:48, Bruce Evans wrote:
>> Perhaps you can find some ideas, answers and PRNG comparison in the
>> original paper:
>> http://www.firstpr.com.au/dsp/rand31/p1192-park.pdf
>
> The ones with Mersenne primes and tweaked Mersenne primes in the reference
> (lanl?) given by pfg@ seem OK.
On 31.05.2016 8:53, Bruce Evans wrote:
> On Tue, 31 May 2016, Andrey Chernov wrote:
>
>> On 31.05.2016 6:42, Bruce Evans wrote:
>>>
>>> Er, I already said which types are better -- [u]int_fast32_t here.
>>
>> [u]int_fast32_t have _at_least_ 32 bits. int
On 31.05.2016 6:42, Bruce Evans wrote:
>
> Er, I already said which types are better -- [u]int_fast32_t here.
[u]int_fast32_t have _at_least_ 32 bits. int32_t in the initial PRNG can
be changed since does not overflow and involve several calculations, but
uint_fast32_t is needed just for two
On 30.05.2016 6:09, Bruce Evans wrote:
> On Sun, 29 May 2016, Conrad Meyer wrote:
>
>> Does clang actually generate different code with this change?
>
> It should, on exotic arches.
>
>> On Sun, May 29, 2016 at 9:39 AM, Andrey A. Chernov
>> wrote:
>>> Log:
>>> Micro
On 30.05.2016 5:17, Bruce Evans wrote:
> On Sun, 29 May 2016, Andrey A. Chernov wrote:
>
>> Log:
>> 1) Unifdef USE_WEAK_SEEDING since it is too obsolete to support and
>> makes
>> reading hard.
>
> Good.
>
>> 2) Instead of doing range transformation in each and every function
>> here,
>> do
On 29.05.2016 22:39, Conrad Meyer wrote:
> Does clang actually generate different code with this change?
Yes, without -O it generates
andl$2147483647, ...
With -O nothing is changed.
In general, it can be not clang and I see no point to left junk code in
any case.
>
> On Sun, May 29, 2016
On 22.05.2016 3:29, Pedro F. Giffuni wrote:
> static void
> srand(unsigned int seed)
> {
>
> + if (seed == 0)
> + seed = 1;
> srandom(seed);
> }
IMHO it is not needed. srandom() already handles seed == 0 case, there
is no point to remap it to another constant.
On 22.05.2016 3:06, Bruce Evans wrote:
> On Sat, 21 May 2016, Pedro Giffuni wrote:
>
>> On 05/21/16 16:55, Conrad Meyer wrote:
>>> On Sat, May 21, 2016 at 1:40 PM, Pedro Giffuni wrote:
On 05/21/16 14:05, Conrad Meyer wrote:
> Won't this still return a
On 21.04.2016 9:29, Baptiste Daroussin wrote:
Modified: head/lib/libc/locale/ascii.c
==
--- head/lib/libc/locale/ascii.c Wed Apr 20 20:43:05 2016
(r298366)
+++
On 21.04.2016 3:57, Andrey Chernov wrote:
> On 20.04.2016 23:44, Baptiste Daroussin wrote:
>> Author: bapt
>> Date: Wed Apr 20 20:44:30 2016
>> New Revision: 298367
>> URL: https://svnweb.freebsd.org/changeset/base/298367
>>
>> Log:
>> Check
On 20.04.2016 23:44, Baptiste Daroussin wrote:
> Author: bapt
> Date: Wed Apr 20 20:44:30 2016
> New Revision: 298367
> URL: https://svnweb.freebsd.org/changeset/base/298367
>
> Log:
> Check the returned value of memchr(3) before using it
>
> Reported by:Coverity
> CID:
On 30.03.2016 4:32, Pedro F. Giffuni wrote:
> --- head/lib/libc/stdio/freopen.c Wed Mar 30 01:08:08 2016
> (r297406)
> +++ head/lib/libc/stdio/freopen.c Wed Mar 30 01:32:08 2016
> (r297407)
> @@ -66,7 +66,8 @@ freopen(const char * __restrict file, co
> (void)
On 30.03.2016 9:13, Pedro F. Giffuni wrote:
>*/
> + sverrno = 0;
> if (file == NULL) {
It introduces the bug of touching errno. Previous code does it right
because 'goto finish;' can't happen with (f < 0) where errno is restored
later.
The whole errno code is complex here for
On 07.12.2015 15:09, Konstantin Belousov wrote:
> Author: kib
> Date: Mon Dec 7 12:09:04 2015
> New Revision: 291936
> URL: https://svnweb.freebsd.org/changeset/base/291936
>
> Log:
> Update ctime when atime or birthtime are updated.
Who calls ufs_itimes() and when to process IN_CHANGE flag
On 07.12.2015 17:42, Andrey Chernov wrote:
> On 07.12.2015 15:09, Konstantin Belousov wrote:
>> Author: kib
>> Date: Mon Dec 7 12:09:04 2015
>> New Revision: 291936
>> URL: https://svnweb.freebsd.org/changeset/base/291936
>>
>> Log:
>> Update ctime
On 21.11.2015 5:29, David Sanderson wrote:
> Thank you for pointing out the possibility of fdopen() setting
> FD_CLOEXEC on the parent's end of the pipe if the mode string contains
> an 'e'. This is indeed documented on popen(3).
>
> However, note that popen() uses pipe2(pdes, O_CLOEXEC) to
On 21.11.2015 2:57, Ravi Pokala wrote:
> There's two different things at play - userland resources and kernel
> resources. Both "FILE *iop" and "struct pid *cur" are userland, while the
> descriptors in "pdes" are kernel. We clean up the descriptors in "pdes" in
> call cases, so we're not
On 21.11.2015 1:36, Ravi Pokala wrote:
> Move fdopen() up near other resource allocation like malloc(); do proper
> deallocation on failure later on in the function.
Incorrect. Old code calls fdopen() only in the parent, new one calls
fdopen() before fork(), so its results shared by both
On 21.11.2015 2:20, Andrey Chernov wrote:
> On 21.11.2015 1:36, Ravi Pokala wrote:
>> Move fdopen() up near other resource allocation like malloc(); do proper
>> deallocation on failure later on in the function.
>
> Incorrect. Old code calls fdopen() only in the parent, n
On 10.11.2015 16:36, Baptiste Daroussin wrote:
> On Tue, Nov 10, 2015 at 04:20:38PM +0300, Andrey Chernov wrote:
>> On 10.11.2015 16:04, Baptiste Daroussin wrote:
>>> On Tue, Nov 10, 2015 at 03:48:52PM +0300, Andrey Chernov wrote:
>>>> On 10.11.2015 11:11, Baptiste
1 - 100 of 248 matches
Mail list logo