Skip to content

Revert valueflow split#6991

Merged
firewave merged 19 commits into
cppcheck-opensource:mainfrom
pfultz2:revert-valueflow-split
Nov 22, 2024
Merged

Revert valueflow split#6991
firewave merged 19 commits into
cppcheck-opensource:mainfrom
pfultz2:revert-valueflow-split

Conversation

@pfultz2

@pfultz2 pfultz2 commented Nov 5, 2024

Copy link
Copy Markdown
Contributor

Revert most of the moving passes out of valueflow.cpp. Splitting up valueflow should be organized differently.

@pfultz2

pfultz2 commented Nov 8, 2024

Copy link
Copy Markdown
Contributor Author

The error in CI is unrelated to this PR, and is a failure with getting qt packages on windows:

INFO    : aqtinstall(aqt) v3.1.18 on Python 3.11.9 [CPython MSC v.1938 64 bit (AMD64)]
WARNING : Specified Qt version "6.7.3" did not exist when this version of aqtinstall was released. This may not install properly, but we will try our best.
WARNING : Specified target combination "windows desktop win64_msvc2022_64" did not exist when this version of aqtinstall was released. This may not install properly, but we will try our best.
ERROR   : The packages ['qt_base', 'qtcharts'] were not found while parsing XML of package information!
==============================Suggested follow-up:==============================
* Please use 'aqt list-qt windows desktop --arch 6.7.3' to show architectures available.
* Please use 'aqt list-qt windows desktop --modules 6.7.3 <arch>' to show modules available.

@pfultz2

pfultz2 commented Nov 9, 2024

Copy link
Copy Markdown
Contributor Author

This same failure is on the main branch.

@firewave

firewave commented Nov 16, 2024

Copy link
Copy Markdown
Collaborator

Just looking at the changes files and not the changes it self.

Please revert the *.ts changes.

It also seems you missed to merge back vf_number.cpp and vf_enumvalue.cpp.

@firewave

Copy link
Copy Markdown
Collaborator

I also think the infer.cpp changes are fine and should stay.

@firewave

Copy link
Copy Markdown
Collaborator

vf_debug.cpp also looks like it should be merged back.

@danmar

danmar commented Nov 17, 2024

Copy link
Copy Markdown
Collaborator

Please revert the *.ts changes.

imho the ts files should not be changed behind our backs.

I have always updated the ts files during the release. How do I update the ts files nowadays when qmake support is removed? It would be good to document that step in the createrelease document which I follow when I make the releases.

@danmar

danmar commented Nov 17, 2024

Copy link
Copy Markdown
Collaborator

Please revert the *.ts changes.

I created https://trac.cppcheck.net/ticket/13322

@firewave

Copy link
Copy Markdown
Collaborator

Please revert the *.ts changes.

imho the ts files should not be changed behind our backs.

I have always updated the ts files during the release. How do I update the ts files nowadays when qmake support is removed? It would be good to document that step in the createrelease document which I follow when I make the releases.

That is done implicitly. Only updating them on release never made sense because that means that they will always be out-of-date during development and might render translated versions unusable.

@danmar

danmar commented Nov 18, 2024

Copy link
Copy Markdown
Collaborator

That is done implicitly. Only updating them on release never made sense because that means that they will always be out-of-date during development and might render translated versions unusable.

ok well if you can make it work properly so that they are only updated when I change a related file I am not against it. Paul did not change any related files here in this PR.

@pfultz2

pfultz2 commented Nov 18, 2024

Copy link
Copy Markdown
Contributor Author

Please revert the *.ts changes.

I am not sure what you are talking about. I reverted the actual commits which should revert everything.

@pfultz2

pfultz2 commented Nov 18, 2024

Copy link
Copy Markdown
Contributor Author

It also seems you missed to merge back vf_number.cpp and vf_enumvalue.cpp.

I'll address that in a leter PR.

I also think the infer.cpp changes are fine and should stay.

Let me put those changes back in this PR.

vf_debug.cpp also looks like it should be merged back.

I dont think the pass is significant enough to have in a seperate file.

@firewave

Copy link
Copy Markdown
Collaborator

It also seems you missed to merge back vf_number.cpp and vf_enumvalue.cpp.

I'll address that in a leter PR.

I would prefer if we could revert it all in a single PR.

vf_debug.cpp also looks like it should be merged back.

I dont think the pass is significant enough to have in a seperate file.

That's what I said.

@pfultz2

pfultz2 commented Nov 20, 2024

Copy link
Copy Markdown
Contributor Author

I would prefer if we could revert it all in a single PR.

I would prefer it be merged in quicker so we can avoid major merge conflicts if there is another PR making tweaks to ValueFlow.

@pfultz2

pfultz2 commented Nov 20, 2024

Copy link
Copy Markdown
Contributor Author

vf_debug.cpp also looks like it should be merged back.

I dont think the pass is significant enough to have in a seperate file.

That's what I said.

I see what you are saying now, I'll address that in a follow-up PR.

@pfultz2

pfultz2 commented Nov 20, 2024

Copy link
Copy Markdown
Contributor Author

I also think the infer.cpp changes are fine and should stay.

I reverted those now.

@firewave

Copy link
Copy Markdown
Collaborator

I would prefer it be merged in quicker so we can avoid major merge conflicts if there is another PR making tweaks to ValueFlow.

Yeah - I refrained from publishing ones affecting those. Will take a look later today and will merge if it looks okay. I can also do the remaining reverting immediately after.

@firewave

Copy link
Copy Markdown
Collaborator

I was too tired last night - will take a look when I get back in later. Sorry about that.

Comment thread lib/valueflow.cpp
}
}

static Library::Container::Yield findIteratorYield(Token* tok, const Token** ftok, const Settings& settings)

@firewave firewave Nov 21, 2024

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread lib/valueflow.cpp
runner.run_once({
VFA(valueFlowDynamicBufferSize(tokenlist, symboldatabase, errorLogger, settings)),
VFA(analyzeDebug(tokenlist, errorLogger, settings)), // TODO: add option to print it after each step/iteration
VFA(valueFlowDebug(tokenlist, errorLogger, settings)),

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean the comment?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Nothing to be addressed here. Just to note the differences I spotted during the review.

@firewave firewave left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The *.ts file changes still need to be dropped.

Otherwise it looks fine. Fortunately not many changes (only two commits - unless I missed something) were done to the split out files.

@firewave

Copy link
Copy Markdown
Collaborator

Just drop the .ts changes and we can merge it. The rest can be addressed afterwards.

@firewave firewave left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pushed a commit dropping the .ts changes.

@firewave firewave merged commit 9989e18 into cppcheck-opensource:main Nov 22, 2024
@pfultz2 pfultz2 deleted the revert-valueflow-split branch November 22, 2024 14:35
chrchr-github pushed a commit that referenced this pull request Nov 23, 2024
restores the changes lost in #6991
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants