DDraceNetwork - developer

Learath2

Let me give you one last reason to use zero-terminated strings. They don't have a length limit

neither does size prefixed strings (in a real physical world)

Learath2

fwiw I only looked to spot the presence of 2 loops and I couldn't spot 2 loops

because you only need the inner core of the strlen function in the inner loop of strcpy

Chairn

neither does size prefixed strings (in a real physical world)

you mean in a real theoretical world, unless you want to introduce a branch, length is limited

to detect the null character in the input string

00:03

how is it practically limited when no machine has enough memory to fill 2^64 bytes ?

00:04

anyway, on SIMD, in x86, the glibc function just checks for page boundary on 4kB page

00:04

then it fetches as much as it wants and detects if there's a null character in the data

Chairn

because you only need the inner core of the strlen function in the inner loop of strcpy

yes, after looking at it this was obvious

Chairn

how is it practically limited when no machine has enough memory to fill 2^64 bytes ?

it's not, I'm just being pedantic since they are being pedantic

00:05

my null delimited strings will work for my universe computer with 10 exobyte strings

the first load is a special unaligned ones that performs less good than another instruction which requires an cache aligned (or 32B aligned) address, otherwise it generates a segfault (really not the best exception to generate though)

00:11

note that some ISA allows vector loads to fail in an elegant manner with not touching elements outside the allowed region (edited)

Bamcane

[ddnet/ddnet] Issue opened: #8039 Include colored broadcast from 0.7

We could add a SERVERCAPFLAG to let client know this server send broadcast with color, This is a useful way for players fast know the broadcast type (e.g, database error broadcast use red color)

@Robyt3 i tested on windows ram changes, but it doesnt permanentaly increase

@furo: when fix #8039 (edited)

@Robyt3 i did however indeed have a massive lag closing the console after a while

07:55

@Robyt3 m_Elements defs increases the whole time

07:56

maybe gcc has a different allocation strategy

07:56

so it takes much longer to notice with it

chillerdragon: check dms aka offtopic

chillerdragon: don't make fun of others

On da phone later

Replying to @MilkeeyCat chillerdragon: check dms aka offtopic

ChillerDragon: feel free to DM me about rules, if you want anything clarified

<ChillerDragon> ye sure im actually curious @heinrich5991 where dm

at your service, I'm currently monitoring irc, matrix and discord

<ChillerDragon> do you mind doing it in a public irc channel thats not bridged to ddnet?

08:13

<ChillerDragon> #ddnet-off-topic on quakenet

prefer not to

08:18

interesting: https://sourcehut.org/blog/2021-11-29-announcing-the-chat.sr.ht-public-beta/

Announcing chat.sr.ht: a persistent IRC session for sourcehut users

sourcehut is a network of useful open source tools for software project maintainers and collaborators, including git repos, bug tracking, continuous integration, and mailing lists.

@Robyt3 i think i understand the problem now... it's indeed not a leak, it's just a suboptimal way of doing small allocation if you'd wait long enough it would probably decrease memory again. I'll think about a solution

1

who is cpp pro? i need this: https://en.cppreference.com/w/cpp/container/multimap/lower_bound however in my case the multimap is sorted in a reversed order so i'd also need the reverse of lower_bound basically in other words: "the last element that is still greater (or equal) than key"

cpp/container/multimap/lower bound

08:32

iterators in cpp are so hard

08:32

xd

have you overloaded the operator< to sort in reverse order?

std::multiset<SMemoryHeapQueueElement, std::greater<>>

08:34

this basically

then lower_bound should do what you want, no?

heinrich5991

then lower_bound should do what you want, no?

that's not clear for me from the specs

08:34

xd

08:34

"This overload participates in overload resolution only if the qualified-id Compare::is_transparent is valid and denotes a type. It allows calling this function without constructing an instance of Key."

08:35

this is the hardest sentence i over read

heinrich5991

then lower_bound should do what you want, no?

but that would be the intuitive solution i guess

I'm not sure what else it would return

08:36

it can't suddenly start using something other than your comparator, that would violate its internal guarantees, I guess

i'll simply test it out i guess

seems not to work