◆ C#

Get assembler output from C/C++ source

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFor the C source file 'main.c' and the C++ source file 'utility.cpp', generate the assembler…+
For the C source file 'main.c' and the C++ source file 'utility.cpp', generate the assembler output for both using GCC, targeting an x64 architecture, with optimizations enabled for speed.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I dive into the C/C++ source code, give me the assembler output for…+
Before I dive into the C/C++ source code, give me the assembler output for 'calculate_checksum.c' and 'process_data.cpp', but highlight any instructions that involve memory barriers or atomic operations so I can quickly see the concurrency implications.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm looking at the assembler output for 'crypto_lib.cpp' on an older x86 architecture, trying…+
The customer is complaining about a weird bug in our C++ library only on older CPUs.
I'm looking at the assembler output for 'crypto_lib.cpp' on an older x86 architecture, trying to find where a specific instruction sequence might be causing a crash. It's too much to sift through. Can you pinpoint sections that use deprecated or less common instructions that might behave differently on older hardware, and tell me what the most likely culprit for a memory access error would be?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time manually inspecting assembler output to ensure my C functions are using…+
I keep losing time trying to manually optimize critical C functions for specific CPU instruction sets.
I spend too much time manually inspecting assembler output to ensure my C functions are using the most efficient instructions for specific architectures. What habit should I change to more quickly identify and leverage intrinsic functions or compiler-specific pragmas that could generate better assembly for performance-critical sections, without having to hand-tune every line?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from C#'s own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.