Who would think that? At every corporation where I've worked it's been explicit in both the contract and in HR training that this is explicitly not allowed.
I was chatting with an old classmate at a homecoming a few months ago, and he mentioned that, during the polygraph top get Canadian Top Secret clearance for a co-op job, he had to say how many drinks he had each week. Being a university student, it got brushed aside, but the answer was considered to be alcoholism-level.
In a weird way, that's almost a positive sign, if you view the security-clearance process as mostly being about quickly clearing away secrets that could be used for blackmail down the line, when the person has more authority and more to lose.
P.S.: Further musing: There's a system-design tension between granting access to people that are "perfect" versus "flawed in ways we are aware of and can manage." Where a process ought to land on that spectrum depends on certain assumptions about baseline applicant quality, an estimate of the organization's accuracy at [false/true] [negatives/positives], and the impacts.
If you auto-reject the people who admit to something sub-criminal like cheating on their spouse, that means no applicant will ever admit to it, so you'll end up with more people hid it. In the long run, that means a higher proportion of employees who have something an adversary can use for blackmail, and the blackmail is more-effective because the repercussions are large.
There are co-operatives in manufacturing which would need their staff to be security-cleared in order to win government contacts (such as assembling weapons). Perhaps this is what parent is referring to. Co-ops aren't just for groceries :)
In the Canadian university lingo, co-op refers to a (usually paid) internship that you complete as part of your degree. You usually have a couple co-op terms/semesters along with your traditional terms. For example, you may start your degree with two semesters of classes, then a semester of co-op, then one of classes, then another two co-ops, more classes, etc. until you complete the degree requirements. Degrees with a co-op requirement usually will make mention of it (e.g. Software Engineering with co-op).
That's pretty cool. I'm guessing you're American, not Canadian, right? I didn't realize American schools had co-ops; I thought they mostly/solely had internships.
Interesting, but I am very sceptical. I'd be interested in seeing actual verified results of how it handles a road with heavy snow, where the only lane references are the wheel tracks of other vehicles, and you can't tell where the road ends and the snow-filled ditch begins.
The issue is that it's no longer actually RISC-V M at the point, you're changing the instruction set. If you're compiling RISC-V M code, that doesn't need the extra NOP.
That being said, the disabling of MUL is being done at a software project level here, not by the CPU vendor. It's in the same linked commit that added in the NOP instructions to the arithmetic routines.
If your software runs on any chip and your chip runs any software, you have a problem, but in embedded cases, you know which chip runs which software, because you designed them together.
This is very true and why I'm not liking that Xilinx is trying to go the other way. It really gets in the way and doesn't work. I know what's connected to what and how, but their system device tree generator doesn't and it yells really loud about that. And I don't even need a device tree, just xparameters.h
That's not a reasonable solution. Have you used the Patreon app? I use it regularly on Android, and have dozens of audio podcast files downloaded through it.
I use mine at Costco for purchases over $300 (limit for tap). At least here in Canada, they only accept Mastercard, not Visa, and I don't remember the PIN for my Mastercard.
reply