Page MenuHomeFreeBSD

GCC Warning - unused-but-set-variable
AbandonedPublic

Authored by araujo on Aug 25 2015, 8:23 AM.
Tags
None
Referenced Files
F80140853: D3478.diff
Thu, Mar 28, 12:00 PM
Unknown Object (File)
Sat, Mar 9, 8:08 AM
Unknown Object (File)
Dec 20 2023, 1:19 AM
Unknown Object (File)
Nov 5 2023, 5:40 AM
Unknown Object (File)
Sep 9 2023, 9:21 AM
Unknown Object (File)
Jun 24 2023, 8:43 PM
Unknown Object (File)
May 6 2023, 4:02 AM
Unknown Object (File)
Mar 5 2023, 5:35 PM
Subscribers

Details

Summary

Remove unused variable olm1

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 229
Build 229: arc lint + arc unit

Event Timeline

araujo retitled this revision from to GCC Warning - unused-but-set-variable.
araujo updated this object.
araujo edited the test plan for this revision. (Show Details)
araujo added reviewers: rodrigc, bapt.

Need to send upstream, but the change is too mini less for that right now.

rodrigc edited edge metadata.

Just because the change needs to be submitted upstream, do not give up.
Matt Ahrens can help with changes that need to be pushed upstream to Illumos. @mahrens , can you help with this?

You can use the instructions here: https://github.com/openzfs/openzfs to submit a pull request and get regression tests. Then solicit code reviews to developer@lists.illumos.org.

@araujo : the instructions that @mahrens gave are pretty straightforward. I looked at: https://github.com/openzfs/openzfs/pulls
but did not see you open a pull request. Do you plan to do this?

@araujo : the instructions that @mahrens gave are pretty straightforward. I looked at: https://github.com/openzfs/openzfs/pulls
but did not see you open a pull request. Do you plan to do this?

Not yet, I plan to do this week.

Best,

This patch doesn't apply for Illumos, as their merge.c seems more updated than the one we have.

From Illumos:
292 /*
293 * Don't do the recursive equivalency checking more than
294 * we have to.
295 */
296 if (olm1 == NULL || olm1->ml_type->t_id != ml1->ml_type->t_id) {
297 if (ml1->ml_size != ml2->ml_size ||
298 !equiv_node(ml1->ml_type, ml2->ml_type, ed))
299 return (0);
300 }

I do believe soom we will import these changes from vendor.

Waiting for the next import from vendor.