(See also P46)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 5 2019
Build failure - The Moirai have given mortals hearts that can endure.
Build failure - The Moirai have given mortals hearts that can endure.
Successful build - Chance fights ever on the side of the prudent.
Successful build - Chance fights ever on the side of the prudent.
Regarding static_cast<off_t>(expr): I admit I never got around with the various kinds of casts offered by C++ (when I design SW on my own, I try and avoid casting alltogether). When updating the patch, I can still put it in.
I am sorry, I lost track of this ticket for health reasons. Regarding your questions, it seems I was so occupied by the zip archive problem that I neglected styleguide and common appearance. Here are attempts to answer your observations:
The balcony is not scaled depending on window size while everything else is, so it gives the wrong ratio depending on used window size.
Next upload includes:
Successful build - Chance fights ever on the side of the prudent.
Was broken because previously the cheer order was added first and the rest of the orders thereafter. As per this commit that order was reversed, and the (faulty) cmpUnitAI.Cheer() did not push an order to the front but it replaced all orders (which it should not). D2358.
Successful build - Chance fights ever on the side of the prudent.
Tested and seems to work on first sight, no compile warnings with clang 8.0.1.
Thanks for the fix!
Successful build - Chance fights ever on the side of the prudent.
Build failure - The Moirai have given mortals hearts that can endure.
Successful build - Chance fights ever on the side of the prudent.
Build failure - The Moirai have given mortals hearts that can endure.
Successful build - Chance fights ever on the side of the prudent.
Build failure - The Moirai have given mortals hearts that can endure.
Removes unused variables.
Successful build - Chance fights ever on the side of the prudent.
Build failure - The Moirai have given mortals hearts that can endure.
Successful build - Chance fights ever on the side of the prudent.
Build failure - The Moirai have given mortals hearts that can endure.
Fixes @elexis `s notes.
Successful build - Chance fights ever on the side of the prudent.
Successful build - Chance fights ever on the side of the prudent.
Successful build - Chance fights ever on the side of the prudent.
Thanks for the fix. It would be good to compare the implementation against the paste some day.
Or the new implementation against the removed implementation.
Successful build - Chance fights ever on the side of the prudent.
Use markForTranslation with chat filters too, fix excess semicolons.
Successful build - Chance fights ever on the side of the prudent.
Successful build - Chance fights ever on the side of the prudent.
Related: CGUI::FindObjectUnderMouse, IGUIObject::ChooseMouseOverAndClosest, but Im totally not touching those now.
Successful build - Chance fights ever on the side of the prudent.
Build failure - The Moirai have given mortals hearts that can endure.
In D2353#98463, @Imarok wrote:In D2353#98462, @elexis wrote:In D2353#98374, @Imarok wrote:I think we now had multiple Zen 2 users complaining about crashes.
Got a link?
Just see the ticket and the link in the post above.
Here is another link. https://wildfiregames.com/forum/index.php?/topic/15796-known-problems-please-read-before-posting/&do=findComment&comment=384917
So we allready have Ryzen 3600, 3600X, 3700X and 3800X. So we only miss a crash report of an 3900X user to complete the Ryzen Zen2 series.
Please add a comment with some explanation and the link to the doc.
In D2353#98462, @elexis wrote:In D2353#98374, @Imarok wrote:I think we now had multiple Zen 2 users complaining about crashes.
Got a link?
Just see the ticket and the link in the post above.
The other question I have is whether we should actually call ENSURE in AddTLB.
It sounds better to fail more softly with a red error message?
Wouldn't object to a ticket for that (perhaps we already have a "dont use ENSURE" ticket?).
I think we should in general not use ENSURE in hardware detection but red error warnings instead.
Afaik there is nothing that critical that would justify an ENSURE
Sooner or later the magic numbers will change again I assume.
I don't think so.
Looking at the spec of that CPU(PDF page 75) it seems 0x9 is still reserved.
It sounds useful to add the links in the code, there already are some
Good idea
What does reserved mean?
That the number has no current meaning but is reservered for assigning some meaning in the future.
After this change it means in the worst case it will report a 16-way associative cache when someone just has a 8-way or a 32-way or whatever.
Reporting the correct number of not reporting would be more correct if the number is not known.
Either the magic number is correct for all caches, or there should be a wildcard and the Validate function should be changed to account for that wildcard?
(I have no clue what Im talking about)
Seems like ;P
The issue is: we currently don't know what this 0x9 means. But everyone who played 0ad and got this 0x9 had a CPU with a L3 16-way associative cache.
And to be honest: I don't even know why we need this information at all...
In D2353#98374, @Imarok wrote:I think we now had multiple Zen 2 users complaining about crashes.
The one in https://wildfiregames.com/forum/index.php?/topic/27095-cachecpp43-assertion-failed-cachevalidate/ also has this 0x9 and a 16-way associative cache.
So I assume it's correct.
In D2353#98445, @elexis wrote:It seems like you know more than the rest of us about this issue, you have many facts gathered.
I just went down the rabbit hole a bit xD
(Plus some knowledge about how a CPU works internally)
Successful build - Chance fights ever on the side of the prudent.
Successful build - Chance fights ever on the side of the prudent.
Rebased.