Skip to content

Work around weird g++ bug #4509

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roystgnr merged 1 commit into from
Aug 4, 2026
+1 −4
Merged

Work around weird g++ bug #4509

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions src/systems/system_io.C
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -642,10 +642,7 @@ std::size_t System::read_serialized_blocked_dof_objects (const dof_id_type n_obj
std::vector<unsigned int> vars_to_read (_written_var_indices);

if (var_to_read != libMesh::invalid_uint)
{
vars_to_read.clear();
vars_to_read.push_back(var_to_read);
}
vars_to_read.assign({var_to_read});

@jwpeterson jwpeterson Aug 2, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Was calling assign() actually necessary to work around the bug or would the (arguably simpler)

vars_to_read = {var_to_read};

have sufficed as well?

@roystgnr roystgnr Aug 4, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Huh - yes, that works too, as does assign(1, var_to_read). I've no clue why it's just the push_back() that gave me pushback. Irony?


const unsigned int
sys_num = this->number(),
Expand Down