Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Exploring Linux command-line space time

fabiensanglard.net

Post reply on HN
Print view View original

11–20 of 39 posts

Re: Exploring Linux command-line space time

#11

Post by perrygeo »

fsckboy wrote: post #6

this is a small personal nit complaint, but increasingly I see "Linux command-line" used to refer to things which have nothing to do with command-lines per se, which to me suggests some cli-fu with p|pes || other tricky \\&\\&& if-fi $(things). Perhaps we need some better vocabulary to separate these ideas, but the world of unix includes "shell" ideas, and their interplay with cli, there's ascii text ttys, there's an…

"Exploring a C program's memory use over time, on Linux" would be more accurate. Nothing in this article deals with our three spatial dimensions, the typical use of the word "space".

Re: Exploring Linux command-line space time

#12

Post by robbintt »

perrygeo wrote: post #11
fsckboy wrote: post #6

this is a small personal nit complaint, but increasingly I see "Linux command-line" used to refer to things which have nothing to do with command-lines per se, which to me suggests some cli-fu with p|pes || other tricky \\&\\&& if-fi $(things). Perhaps we need some better vocabulary to separate these ideas, but the world of unix includes "shell" ideas, and their interplay with cli, there's ascii text ttys, there's an…

"Exploring a C program's memory use over time, on Linux" would be more accurate. Nothing in this article deals with our three spatial dimensions, the typical use of the word "space".

For software contexts, we refer to space as memory or overall storage depending on the architecture.

Re: Exploring Linux command-line space time

#13

Post by skitter »

Wow, Collect2 sounds kinda hacky based on the linked documentation¹:

- There is user code that needs to run before main. With C/C++ allowing separate compilation, the compiler invocation that creates the entrypoint doesn't know about all of these static constructors.

- Therefore Collect2 pretends to be ld; when invoked, it tries to call the real ld and examines its output

- It creates a c file with a table containing any constructor symbols it finds, then compiles that

- Finally it links the program again, together with the new object file

¹: https://gcc.gnu.org/onlinedocs/gccint/Collect2.html

Re: Exploring Linux command-line space time

#14

Post by fabiensanglard »

skitter wrote: post #13

Wow, Collect2 sounds kinda hacky based on the linked documentation¹: - There is user code that needs to run before main. With C/C++ allowing separate compilation, the compiler invocation that creates the entrypoint doesn't know about all of these static constructors. - Therefore Collect2 pretends to be ld; when invoked, it tries to call the real ld and examines its output - It creates a c file with a table containing…

Thank you for the explanation I did not have the courage to gather.

Re: Exploring Linux command-line space time

#16

Post by perrygeo »

robbintt wrote: post #12
perrygeo wrote: post #11

Earlier quoted context omitted.

"Exploring a C program's memory use over time, on Linux" would be more accurate. Nothing in this article deals with our three spatial dimensions, the typical use of the word "space".

For software contexts, we refer to space as memory or overall storage depending on the architecture.

Yet when refering to both space and time, you should consider explicating that space = memory, time = time.

Re: Exploring Linux command-line space time

#17

Post by thewakalix »

perrygeo wrote: post #11
fsckboy wrote: post #6

this is a small personal nit complaint, but increasingly I see "Linux command-line" used to refer to things which have nothing to do with command-lines per se, which to me suggests some cli-fu with p|pes || other tricky \\&\\&& if-fi $(things). Perhaps we need some better vocabulary to separate these ideas, but the world of unix includes "shell" ideas, and their interplay with cli, there's ascii text ttys, there's an…

"Exploring a C program's memory use over time, on Linux" would be more accurate. Nothing in this article deals with our three spatial dimensions, the typical use of the word "space".

TFA covered more than just C programs.

Re: Exploring Linux command-line space time

#19

Post by ryukoposting »

skitter wrote: post #13

Wow, Collect2 sounds kinda hacky based on the linked documentation¹: - There is user code that needs to run before main. With C/C++ allowing separate compilation, the compiler invocation that creates the entrypoint doesn't know about all of these static constructors. - Therefore Collect2 pretends to be ld; when invoked, it tries to call the real ld and examines its output - It creates a c file with a table containing…

The words "undefined reference to '__main'" give me war flashbacks.

Re: Exploring Linux command-line space time

#20

Post by perrygeo »

thewakalix wrote: post #17
perrygeo wrote: post #11

Earlier quoted context omitted.

"Exploring a C program's memory use over time, on Linux" would be more accurate. Nothing in this article deals with our three spatial dimensions, the typical use of the word "space".

TFA covered more than just C programs.

And what exactly does TFA have to do with this conversation? It's literally not mentioned in the link or these comments (currently).
Post reply on HN