Pelles C forum
Pelles C => Announcements => Topic started by: Pelle on June 05, 2021, 11:22:29 AM
-
This is a second preview of Pelles PE/COFF Viewer (pope.exe): a GUI program for looking into executable, archive (library), object, and debug files. It will be included in a future setup of Pelles C.
- Added X86/X64 disassembler (very basic, no symbolic names etc.)
- Added a few more bits of information
- Fixed a few problems
(compiled with new compiler and C runtime, so watch out...)
www.smorgasbordet.com/pellesc/extra/pope.zip (this link will obviously go dead at some point in the future, but will stay there for now)
-
Got it - gonna try it....
John Z
-
Very good, thank you Pelle!
Try it with some exe and obj files, works well.
-
Super,
Very useful.
-
Very good, thank you Pelle!
Try it with some exe and obj files, works well.
Good news. Thanks!
-
It seems to work great for me!
Good job. ;)
-
so... 3-0... starting to sound like maybe not a total failure, then... cool... 8)
-
so... 3-0... starting to sound like maybe not a total failure, then... cool... 8)
Make that 4-0 ... you are approaching statistical significance. ;D
Side note -- I routinely compile and test BCX using 5 different compilers. I recently
re-enabled 'optimize speed' using your compiler and was stunned to learn
your code generation outperformed all the other compilers by as much as 30%.
It seems you have several super powers!
-
Seems to be working very well on my end, too, I think it will make a nice addition to the compiler suite.
One question, though: how did you implement the splitter control? There are a few examples on the web (there's one on smorgasbordet, too), but in these the widths of the treeview/listview are being changed in realtime, which can generate a lot of flicker, especially with the treeview. Yours seems to work the "right way", i.e. it updates the controls on drag release only.
Regards,
Adrian
-
Side note -- I routinely compile and test BCX using 5 different compilers. I recently
re-enabled 'optimize speed' using your compiler and was stunned to learn
your code generation outperformed all the other compilers by as much as 30%.
It seems you have several super powers!
Dumb luck, more likely... :P
Over a wide range of applications I suspect GCC/LLVM will beat me on most of them. Sometimes the decision to call a runtime function vs using a compiler generated "inlined" version can make a big difference. Maybe even the best can get it slightly wrong at times...?
30% sounds like very much... :o Does this compiler have an option to disable the sleep() between statements? ;D
-
One question, though: how did you implement the splitter control? There are a few examples on the web (there's one on smorgasbordet, too), but in these the widths of the treeview/listview are being changed in realtime, which can generate a lot of flicker, especially with the treeview. Yours seems to work the "right way", i.e. it updates the controls on drag release only.
It goes something like this:
In WM_LBUTTONDOWN handler:
SetCapture(hwnd);
g_xDivider = <start position>;
DrawResizeLine(hwnd, g_xDivider);
In WM_MOUSEMOVE handler:
if (hwnd == GetCapture()) {
DrawResizeLine(hwnd, g_xDivider);
g_xDivider = <new position>;
DrawResizeLine(hwnd, g_xDivider);
}
In WM_LBUTTONUP handler:
if (hwnd == GetCapture()) {
ReleaseCapture();
DrawResizeLine(hwnd, g_xDivider);
ResizeWorkspace();
}
static void DrawResizeLine(HWND hwnd, int x) {
UpdateWindow(hwnd);
HDC hdc = GetDC(hwnd);
if (hdc) {
PatBlt(hdc, x - CXDIVIDER/2, g_rcDivider.top, CXDIVIDER,
g_rcDivider.bottom - g_rcDivider.top, DSTINVERT);
ReleaseDC(hwnd, hdc);
}
}
static void ResizeWorkspace(void) {
HDWP hdwp = BeginDeferWindowPos(4 /* number of windows */);
if (hdwp != NULL) {
hdwp = DeferWindowPos(hdwp, <some window handle #1>, other params...);
hdwp = DeferWindowPos(hdwp, <some window handle #2>, other params...);
hdwp = DeferWindowPos(hdwp, <some window handle #3>, other params...);
hdwp = DeferWindowPos(hdwp, <some window handle #4>, other params...);
EndDeferWindowPos(hdwp);
}
}
Using BeginDeferWindowPos(), DeferWindowPos(), EndDeferWindowPos() is the key to reduce flicker.
DrawResizeLine() is using DSTINVERT, which means the second time you call the function with the same coordinates it will cancel out the first call (removing the line from the screen).
Easy. :P
-
:) Good stuff, thanks very much!
-
Nice, a fresh view for files 8)
-
Nice, a fresh view for files 8)
Glad you think so, since you kicked off this project in the first place... thanks! :)
-
Where is it?
I downloaded an old version!
-
I also tried it with several files. It does work great. Very well done! :)
-
Version 0.99 is the last version.
Would be a good idea to copy into the clipboard only one line rather than all the code.
-
I also tried it with several files. It does work great. Very well done! :)
Thanks! :)
-
Version 0.99 is the last version.
Would be a good idea to copy into the clipboard only one line rather than all the code.
Something to consider for a later version, I think.
-
Question 1:
It seems every DLL file I look at, even old 32 bit from PellesC 9, show under the "Image_File_Header" section item "Machine" they all show "IMAGE_FILE_MACHINE_AMD64". So I checked the flags of the LineCount.DLL and see a macro ASFLAGS -AAMD64 -Gr now I'm on a I7 10th gen so probably my mistake. However every PellesC 9 Add-in DLL showed the same AMD64 machine.
Is it right?
Question 2:
I use the version control in the LineCount.dll in explorer right click on properties shows the version under details. Using PE/COFF viewer on the DLL under the '.rsrc' section, IMAGE_RESOURCE_DIRECTORY (types) I see Major and Minor version entries but they don't show the version information.
Is it different version from somewhere else?
-------
You can probably tell I'm a novice at using a tool like this :)
John Z
-
Q1:AMD64 rather than INTEL is because they were the first to implement that instruction set.
If you have a CPU INTEL that works, this is a generic name.
You can probably tell I'm a novice at using a tool like this
That is better that misunderstanding.
They are people that say they have understood to hide the fact they don't know.
I hope you will have more questions like this.